CoherenceApplication · Oracle

CVE-2026-35308

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Centralized Third Party Jars). 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. While the vulnerability is in Oracle Coherence, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 confidence

This is a critical unauthenticated remote code execution vulnerability in Oracle Coherence's Centralized Third Party Jars component. An attacker with network access via HTTP can exploit this flaw to achieve complete takeover of the Oracle Coherence server, potentially impacting additional products in the environment due to scope change. The CVSS 10.0 score indicates trivial exploitability with no user interaction required.

MitigationApply the Oracle Coherence patch for this vulnerability or upgrade to a patched version. If immediate patching is not possible, restrict network access to Coherence HTTP endpoints using network segmentation or a web application firewall.

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
CoherenceApplication
Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0= 15.1.1.0.0

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Oracle Coherence version
    Check the Coherence installation directory for version files, or examine the coherence.jar manifest, or query the Coherence MBean via JMX/management interface for product version
    Affected 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
  2. Determine if Centralized Third Party Jars is enabled
    Review Coherence configuration files (coherence-cache-config.xml, tangosol-coherence.xml, or operational configuration) for the Centralized Third Party Jars feature or related classloader configuration
    Affected if Centralized Third Party Jars feature is configured or enabled in the Coherence configuration
  3. Verify HTTP network exposure of Coherence endpoints
    Scan network accessible ports and review firewall/load balancer rules to confirm HTTP-based Coherence REST endpoints, MBean over HTTP, or similar management interfaces are externally accessible
    Affected if Coherence HTTP-based endpoints are reachable from untrusted network segments

You are affected if you have an affected Coherence version with Centralized Third Party Jars enabled and HTTP network access is exposed to the Coherence server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Coherence patch for this vulnerability or upgrade to a patched version. If immediate patching is not possible, restrict network access to Coherence HTTP endpoints using network segmentation or a web application firewall.

Fix this in Coherence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35308 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35308 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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