CVE-2026-60281
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 · uneditedVulnerability 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 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 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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 · high confidenceOracle Coherence Core component contains an easily exploitable vulnerability allowing unauthenticated attackers with access to the physical network segment to compromise the Coherence data grid. Successful exploitation grants high confidentiality and integrity impacts, enabling unauthorized creation, deletion, modification, or read access to all data accessible through the Coherence cache. The vulnerability has no availability impact and does not require any privileges or user interaction.
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= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0= 15.1.1.0.0CVSS 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
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Coherence is installedSearch for Coherence processes or services: on Linux 'ps -ef | grep -i coherence' or check for coherence-related Java processes; on Windows check services for 'Coherence' or 'Oracle Coherence'Affected if No Coherence process or service is found (not affected)
-
Determine installed Coherence versionCheck Coherence JAR manifest or version file. Common locations: look for coherence.jar in installation directories, check META-INF/MANIFEST.MF inside coherence*.jar files, or query the Coherence cluster member version via JMX/MBean if accessibleAffected if 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
-
Verify Coherence network ports are exposedCheck for listening Coherence ports (typically TCP ports 7xxx for TcpRing/cluster communication). Run 'netstat -an | grep -E "7[0-9]{3}"' or 'ss -tlnp | grep -E "7[0-9]{3}"' to identify exposed cluster portsAffected if Coherence cluster ports are listening and bound to network interfaces accessible from adjacent network segments
-
Assess network accessibility of CoherenceReview firewall rules and network configuration to determine if Coherence ports are accessible from the adjacent physical network segment. Check if ports are bound to 0.0.0.0 vs localhost-onlyAffected if Coherence ports are accessible from network segments beyond the local host, especially from adjacent physical network segments
Environment 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 the Coherence cluster ports are accessible from the adjacent network segment.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle's latest security patches for Oracle Coherence versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. As a compensating control, implement network segmentation to restrict access to the Coherence cluster to only trusted network segments.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60281 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60281 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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