dbcve.org
CoherenceApplication · Oracle

CVE-2026-60228

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

Unauthenticated remote code execution vulnerability in Oracle Coherence Core component allowing complete system takeover via network TCP access without authentication. Affects versions 12.2.1.4.0 through 15.1.1.0.0 with critical CVSS 9.8 rating indicating full compromise of confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update (CPU) containing the Coherence fix; if immediate patching is not feasible, restrict network access to Coherence TcpCluster ports via firewall or network segmentation to limit attack surface.

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 if Oracle Coherence is installed
    Search for Coherence installation directories (commonly under ORACLE_HOME/coherence or in the Java classpath), or check for coherence*.jar files on the system. Look for processes named 'coherence' or applications using the Coherence library.
    Affected if Oracle Coherence software is found on the system
  2. Determine the installed Coherence version
    Check the coherence-core.jar MANIFEST.MF file for the Implementation-Version attribute, or run: java -jar coherence.jar -version. Also check any version.txt or README files in the Coherence installation directory.
    Affected if The version matches exactly 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0
  3. Identify exposed Coherence listener ports
    Check network configuration for Coherence ports (default ports include 9000-9100 range for cluster, 20000-20010 for HTTP). Use netstat or ss commands: netstat -anp | grep -i coherence, or review application configuration files for configured listen addresses.
    Affected if Coherence ports are bound to accessible network interfaces (0.0.0.0) rather than localhost only
  4. Verify network accessibility of Coherence services
    From an external system, attempt TCP connection to the identified Coherence ports using telnet or nc: telnet <host> <port>. This confirms the vulnerability is network-exploitable without authentication.
    Affected if Coherence TCP ports are reachable from untrusted network segments or the internet

The system is affected if Oracle Coherence is running with version 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 and its TCP-based listener ports are network-accessible.

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 (CPU) containing the Coherence fix; if immediate patching is not feasible, restrict network access to Coherence TcpCluster ports via firewall or network segmentation to limit attack surface.

Fix this in Coherence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60228 — 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-60228 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