CVE-2026-60269
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 · high confidenceUnauthenticated remote code execution vulnerability in Oracle Coherence Core component. The critical CVSS 9.8 score with full CIA (Confidentiality, Integrity, Availability) high impacts indicates a severe flaw exploitable over network without any credentials or user interaction, allowing complete system takeover.
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 installationSearch for coherence JAR files (coherence.jar, coherence-[version].jar) in the filesystem, or look for coherence processes using 'ps aux | grep -i coherence' or check for coherence-related directories in ORACLE_HOME or middleware homesAffected if No Coherence installation found means not affected; presence of Coherence requires further version checking
-
Determine Coherence versionCheck the coherence JAR manifest file (META-INF/MANIFEST.MF inside coherence.jar) for Implementation-Version, or look for version files in the coherence installation directory, or query the Coherence MBean via JMX if accessibleAffected 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 means affected; other versions mean not affected
-
Check for exposed TCP listenersRun 'netstat -an | grep -E "(2000[0-9]|2[0-9]{4})"' or 'ss -tlnp | grep -i coherence' to identify Coherence listening ports, or check coherence-config.xml for <listen-host> and <listen-port> settingsAffected if Coherence TCP ports are bound to 0.0.0.0 (all interfaces) rather than localhost only means the vulnerable service is network-accessible
-
Verify network accessibilityConfirm the Coherence port is reachable from untrusted networks by checking firewall rules (iptables -L, AWS security groups, etc.) and whether the server is on a DMZ or directly internet-facingAffected if Coherence ports are reachable from unauthenticated network attackers means the RCE vulnerability is exploitable in the environment
You are affected if your environment runs Oracle Coherence versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 with Coherence Core TCP ports exposed to untrusted networks.
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 security patches for affected versions (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0) immediately. Until patched, restrict network access to Coherence TCP ports via firewall or network segmentation.
Oracle Coherence version with CVE-2026-60269 fix (consult Oracle Critical Patch Update)
- 1. Review Oracle Critical Patch Update advisories for CVE-2026-60269 to obtain the specific patch or fixed version
- 2. For Oracle Coherence 12.2.1.4.0, apply the corresponding patch from Oracle's Critical Patch Update or upgrade to a later 12.2.1.4.x patch set
- 3. For Oracle Coherence 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0, upgrade to the next available patch set or the version indicated in the Oracle Critical Patch Update advisory
- 4. Test the upgrade in a non-production environment before deploying to production
- 5. Verify the fix by confirming the Coherence version matches the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.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 $9,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60269 — 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-60269 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