dbcve.org
CoherenceApplication · Oracle

CVE-2026-60257

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 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 affecting versions 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 takeover due to easily exploitable flaw in deserialization or similar core functionality.

MitigationApply Oracle Critical Patch Update for Coherence immediately. If patches cannot be applied, restrict network access to Coherence listener ports and disable untrusted deserialization filters.

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:= 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 and version
    Locate Oracle Coherence installation directory and check version manifest files (such as coherence.jar MANIFEST.MF, coherence-build.properties, or product version files in the installation root). Compare the discovered version against 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0.
    Affected if The installed version matches exactly 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0.
  2. Confirm Coherence process is running
    Use system process listing commands (such as ps, tasklist, or service management tools) to identify running Java processes associated with Oracle Coherence. Look for coherence.jar or related Coherence classpath entries in process details.
    Affected if A Coherence process is actively running on the system.
  3. Check network exposure of Coherence ports
    Use netstat, ss, or similar network tools to identify open TCP listening ports associated with the Coherence process. Determine if these ports are bound to 0.0.0.0 or an accessible network interface rather than localhost only.
    Affected if Coherence TCP ports are listening on accessible network interfaces (non-localhost bindings) and reachable from the network.
  4. Verify network accessibility from untrusted sources
    Review firewall rules, network ACLs, or cloud security groups to determine whether external or untrusted network segments can reach the Coherence listening ports. Use port scanning tools from external hosts to confirm reachability.
    Affected if The Coherence service port is reachable from network segments that should not have access (such as the internet or untrusted VLANs).

A system is affected if it runs Oracle Coherence version 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 with network-accessible TCP ports, regardless of authentication or user interaction.

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 for Coherence immediately. If patches cannot be applied, restrict network access to Coherence listener ports and disable untrusted deserialization filters.

Fix this in Coherence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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