dbcve.org
CoherenceApplication · Oracle

CVE-2026-60224

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via TCP to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Critical unauthenticated remote code execution vulnerability in Oracle Coherence Core component affecting versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Allows attackers with network access via TCP to achieve complete system compromise ( Confidentiality, Integrity, Availability) without any authentication credentials.

MitigationApply Oracle Critical Patch Update patches for Coherence; restrict network exposure of Coherence ports using firewall rules or network segmentation until patches can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoherenceApplication
Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0= 15.1.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Coherence installation
    Locate Coherence installation directories and check for coherence.jar or coherence.war files. Common locations include Oracle Middleware home directories or WebLogic installations with Coherence modules.
    Affected if Coherence software is present on the system
  2. Determine installed Coherence version
    Check version information in Coherence manifest files, coherence.jar META-INF/MANIFEST.MF, or run coherence version command if available. Compare against the affected versions: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0.
    Affected if Installed version matches exactly one of: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0
  3. Identify Coherence network listeners
    Review Coherence configuration files (tangosol-coherence.xml, coherence-cache-config.xml) and running process network bindings. Use netstat or similar tools to identify ports where Coherence listens for TCP connections (typically port 7574 for cluster communication, or custom ports as configured).
    Affected if Coherence is listening on accessible TCP ports
  4. Verify TCP network exposure
    Assess network accessibility of Coherence ports from untrusted networks. Check firewall rules, exposed network interfaces, and whether Coherence listens on 0.0.0.0 or only on localhost/trusted interfaces.
    Affected if Coherence TCP ports are reachable from network segments beyond trusted administration networks

A user is affected if they have exactly one of the listed Coherence versions (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0) AND their Coherence TCP ports are accessible from network locations where untrusted actors could connect.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update patches for Coherence; restrict network exposure of Coherence ports using firewall rules or network segmentation until patches can be applied.

Fix this in Coherence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60224 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data