dbcve.org
CoherenceApplication · Oracle

CVE-2026-60220

CRITICAL · 9.3 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 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 require human interaction from a person other than the attacker and while the vulnerability is in Oracle Coherence, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Coherence accessible data as well as unauthorized access to critical data or complete access to all Oracle Coherence accessible data. CVSS 3.1 Base Score 9.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N).

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 · moderate confidence

Critical unauthenticated vulnerability in Oracle Coherence Core component allows remote attackers via TCP to modify or access critical data. Requires human interaction and has scope change implications, affecting versions 12.2.1.4.0 through 15.1.1.0.0.

MitigationApply Oracle's available security patches for the affected Coherence versions immediately. Until patched, restrict network access to Coherence ports and monitor for suspicious TCP activity.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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
    Check for Oracle Coherence installation directories or look for coherence.jar files. Common locations include $ORACLE_HOME/coherence, /opt/oracle/coherence, or search for 'coherence' in installed packages using 'rpm -qa | grep -i coherence' or 'ls -la' in Oracle middleware directories.
    Affected if Oracle Coherence software is present on the system
  2. Determine the installed Oracle Coherence version
    Check the coherence.jar manifest or version files. Look for VERSION.txt, manifest.mf inside coherence.jar, or check the product installation directory for version information. The version is typically listed in the product documentation or startup logs.
    Affected if The installed 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. Verify network exposure of Coherence ports
    Identify Coherence ports in use (commonly 7574 for cluster discovery, 20000+ for TCMP). Use 'netstat -tulpn' or 'ss -tulpn' to list listening ports, then determine if these ports are bound to non-localhost interfaces (0.0.0.0 or external IP) versus localhost only (127.0.0.1).
    Affected if Coherence TCP ports are listening on 0.0.0.0 or external network interfaces accessible to untrusted sources
  4. Confirm the Core cache functionality is in use
    Review Coherence configuration files (cache-config.xml, tangosol-coherence.xml) for <cache-config> definitions that use the Core cache scheme. Check application logs for cache operations or review deployment descriptors that reference Coherence caches.
    Affected if The Coherence Core component cache scheme is configured and actively used by applications

You are affected if Oracle Coherence is installed with a version exactly matching 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 and the Coherence TCP ports are network-accessible from untrusted sources.

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's available security patches for the affected Coherence versions immediately. Until patched, restrict network access to Coherence ports and monitor for suspicious TCP activity.

Fix this in Coherence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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