dbcve.org
CoherenceApplication · Oracle

CVE-2026-60261

HIGH · 8.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 →
93/100
Remediation priority · Urgent
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 access to the physical communication segment attached to the hardware where the Oracle Coherence executes to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/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

Oracle Coherence vulnerability in the Core component allows an unauthenticated attacker with physical network segment access to compromise the product. The attack requires network adjacency (not remote internet), has low complexity, no privileges needed, and results in complete confidentiality, integrity, and availability takeover.

MitigationApply Oracle patches for the affected versions (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0) when available. Until then, enforce strict network segmentation and restrict physical/local network access to Oracle Coherence infrastructure.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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
    Search for coherence-related directories, JAR files (coherence*.jar), or coherence binaries in common locations such as $ORACLE_HOME, /opt/oracle, or C:\Oracle. Also check for coherence processes running via 'ps aux | grep -i coherence' or tasklist on Windows.
    Affected if Oracle Coherence software is found on the system
  2. Determine installed Coherence version
    Check the coherence JAR manifest: locate coherence.jar or coherence-core.jar and run 'unzip -p coherence.jar META-INF/MANIFEST.MF' to read the Implementation-Version. Alternatively, check the product's README, version file, or run the coherence version command if available.
    Affected if The version matches 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 exactly
  3. Confirm Coherence Core component is in use
    Review application configuration files (typically XML files in conf/ or config/ directories) for coherence-config or cache configuration definitions that reference the coherence core tier. Check startup scripts for coherence core tier initialization.
    Affected if Coherence Core component is configured and actively used by the deployment
  4. Assess network exposure of Coherence service
    Review network configuration for Coherence listener ports (default ports 7, 8088, 9000-9010, or custom ports defined in tangosol-coherence-override.xml). Use 'netstat -an | grep <port>' or equivalent to identify exposed interfaces.
    Affected if Coherence ports are listening on network-accessible interfaces (non-localhost)

The environment is affected if Oracle Coherence is installed with version 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 and the Coherence Core component is exposed to network access.

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 patches for the affected versions (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0) when available. Until then, enforce strict network segmentation and restrict physical/local network access to Oracle Coherence infrastructure.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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