CVE-2026-35310
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 HTTP 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 confidenceA pre-authentication remote code execution vulnerability in Oracle Coherence's Core component (versions 12.2.1.4.0 through 15.1.1.0.0), exploitable via HTTP without credentials, allowing an unauthenticated attacker to achieve 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 installed Oracle Coherence versionLocate the Coherence installation directory and check the version file or use the Coherence version command (coherence.version or coherence -version). Common locations include the Oracle middleware home or coherence/lib directories. Check manifest files or version.properties files within the Coherence installation.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.
-
Confirm Coherence Core component is in useExamine the Coherence configuration files (typically coherence.xml, tangosol-coherence.xml, or the application's coherence-cache-config.xml) to verify the Core component is configured and actively used for data grid operations.Affected if Coherence Core is deployed and actively processing data grid requests.
-
Verify HTTP network exposure of Coherence endpointsCheck network listeners and port configurations for Coherence HTTP-based management or data endpoints. Review the Coherence over HTTP configuration in the deployment descriptor or startup scripts to identify exposed HTTP ports (commonly 20000-20099 range for Coherence*Extend or management ports).Affected if Coherence HTTP endpoints are accessible over the network without authentication requirements.
-
Check for unauthenticated HTTP access enabledReview the Coherence security configuration (coherence-security-config.xml or security settings in the main coherence.xml) to determine if unauthenticated access is permitted for the HTTP-based API or management interfaces.Affected if Unauthenticated HTTP access to Coherence endpoints is permitted in the security configuration.
You are affected if your environment runs Oracle Coherence version 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 with the Core component exposed via unauthenticated HTTP network access.
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 Critical Patch Updates addressing this vulnerability or upgrade to a patched version of Oracle Coherence; implement network segmentation and WAF rules as interim compensating controls until patching is complete.
- Consultation3.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35310 — 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-35310 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