CVE-2026-60306
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 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 · moderate confidenceOracle Coherence contains a critical vulnerability in its core component that allows unauthenticated attackers with network access via TCP to achieve complete system compromise, including full confidentiality, integrity, and availability impacts. The vulnerability affects versions 12.2.1.4.0 through 15.1.1.0.0 and is easily exploitable without any authentication 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Coherence installation and versionLocate Oracle Coherence installation directories and check version information in product metadata, manifest files, or version-specific libraries. Common locations include ORACLE_HOME directories or Coherence JAR file manifests.Affected if The installed version matches 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 exactly.
-
Determine if Coherence listener ports are exposed on network interfacesReview network configuration and firewall rules to identify which ports the Coherence Core component is bound to. Use netstat, ss, or equivalent tools to list listening ports and their binding addresses.Affected if Coherence TCP listener ports are bound to network-accessible interfaces (0.0.0.0 or non-loopback addresses) rather than localhost only.
-
Verify network accessibility of Coherence serviceFrom an external host, attempt to reach the Coherence ports over TCP to confirm the service is reachable. Check ACLs, firewall rules, and network segmentation configurations.Affected if The Coherence ports are reachable from untrusted network segments or the internet.
-
Review Coherence configuration for unauthenticated access exposureExamine Coherence configuration files (typically XML-based cache configuration or tangosol-coherence.xml) for settings that control authentication and session handling on exposed endpoints.Affected if The configuration permits unauthenticated or unauthenticated remote invocations on the exposed TCP listener.
You are affected if Oracle Coherence version 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 is installed AND the Coherence TCP listener is accessible over the network without authentication.
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.
dbcve · scopedApply Oracle Critical Patch Updates or specific patches for CVE-2026-60306 to all affected Coherence installations. If immediate patching is not possible, restrict network access to Coherence ports and implement additional network segmentation to limit exposure.
Apply latest Oracle Critical Patch Update (CPU) containing fix for CVE-2026-60306
- 1. Navigate to Oracle Critical Patch Updates and Security Alerts at https://www.oracle.com/security-alerts/
- 2. Locate the CPU (Critical Patch Update) that addresses CVE-2026-60306 for Oracle Coherence
- 3. Download the applicable security patch for your specific Oracle Coherence version (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0)
- 4. Review the patch readme for pre-installation requirements and prerequisites
- 5. Apply the patch following Oracle's standard patch application procedures for Oracle Coherence
- 6. After patching, restart Oracle Coherence services as instructed in the patch documentation
- 7. Verify the patch was applied successfully and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60306 — 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-60306 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