Skip to content
major vulnerability· requires attention

Oracle Coherence is widely used enterprise middleware; an unauthenticated RCE allowing full takeover is high-impact and newsworthy across organizations.

Applications

CVE-2026-60227

9.8
Critical
EPSS 0.51%Patch availableJul 22, 2026

Unauthenticated RCE in Oracle Coherence enabling full takeover.

common questions

Is CVE-2026-60227 being exploited?

Not confirmed. CVE-2026-60227 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-60227?

CVE-2026-60227 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60227?

Yes. A fix has been recorded for CVE-2026-60227. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60227 affect?

CVE-2026-60227 affects Oracle Coherence (Oracle Fusion Middleware), 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60227?

Apply vendor patch immediately; if none, isolate Coherence and block TCP access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Coherence (Oracle Fusion Middleware)12.2.1.4.014.1.1.0.014.1.2.0.015.1.1.0.0
impact

Unauthenticated remote code execution over TCP allowing full compromise of Oracle Coherence (confidentiality, integrity, availability loss).

action required

Immediate action required

affected versions
Oracle Corporation Oracle Coherence
  • affected12.2.1.4.0
  • affected14.1.1.0.0
  • affected14.1.2.0.0
  • affected15.1.1.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free