CVE-2026-60277
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. Difficult to exploit 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 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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 confidenceVulnerability in Oracle Coherence Core component allowing unauthenticated remote attackers to achieve complete takeover of the Coherence instance via TCP network access. The CVSS 3.1 score of 8.1 reflects high confidentiality, integrity, and availability impacts, though the 'difficult to exploit' characterization and high attack complexity (AC:H) indicate practical exploitation requires significant effort.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 installationCheck for Coherence installation directories (commonly under ORACLE_HOME/coherence or /opt/oracle/coherence) and look for coherence.jar or coherence-core.jar files. On Linux, run: find / -name 'coherence.jar' 2>/dev/null | head -20Affected if Coherence software is found on the system
-
Determine installed Coherence versionRun: java -jar coherence.jar -version 2>&1 or check manifest files within the coherence JAR for version information. Also check installation logs or ORACLE_HOME/coherence/README for version detailsAffected if 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
-
Verify Coherence TCP listener is exposedCheck for listening ports used by Coherence (default ports include 7574, 8088, 9000, or custom ports configured in tangosol-coherence.xml). Run: netstat -tlnp | grep -E '(7574|8088|9000)' or ss -tlnpAffected if Coherence ports are listening on 0.0.0.0 or an exposed network interface, allowing remote TCP access
-
Confirm Core component is in useReview Coherence configuration files (tangosol-coherence.xml, coherence-cache-config.xml) in the deployment for <distributed-scheme> or <replicated-scheme> definitions that use the Core storage engineAffected if Coherence cache services using the Core component are configured and active
-
Check network accessibility of Coherence portsFrom an external host, test TCP connectivity to Coherence ports: nc -zv <target-ip> 7574 or telnet <target-ip> 7574. Review firewall rules: iptables -L -n or firewall-cmd --list-allAffected if Coherence ports are reachable from untrusted networks or the internet
A system is 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 Core component is accessible via TCP from a network where untrusted users could connect.
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 the relevant Oracle Critical Patch Update (CPU) containing the fix for CVE-2026-60277 to all affected Oracle Coherence installations (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0). If immediate patching is not feasible, restrict network access to Coherence ports at the network perimeter and disable unnecessary Coherence services.
Oracle Coherence 12.2.1.4.x → 12.2.1.4.0 (apply latest CPU patch) or upgrade to 14.1.2.0.0/15.1.1.0.0 with latest security patches; Oracle recommends moving to the most recent supported version (15.1.1.x or later)
- 1. Check Oracle's official Critical Patch Update (CPU) advisory for the quarter containing this CVE at https://www.oracle.com/security-alerts/
- 2. Download and apply the corresponding security patch for Oracle Coherence from Oracle Support (support.oracle.com)
- 3. For version 12.2.1.4.0: Apply Oracle Critical Patch Update that includes the fix, or upgrade to a later supported version
- 4. For version 14.1.1.0.0 and 14.1.2.0.0: Apply the latest Oracle Coherence patch set update (PSU) from Oracle Support
- 5. For version 15.1.1.0.0: Apply the latest available patch from Oracle Support
- 6. After patching, restart all Coherence server processes and validate functionality
- 7. Verify the vulnerability is remediated by reviewing the applied patch documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60277 — 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-60277 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