dbcve.org
CoherenceApplication · Oracle

CVE-2026-35306

CRITICAL · 9.3 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). The supported version that is affected is 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 unauthorized access to critical data or complete access to all Oracle Coherence accessible data as well as unauthorized update, insert or delete access to some of Oracle Coherence accessible data. CVSS 3.1 Base Score 9.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N).

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 vulnerability in Oracle Coherence's Centralized Third Party Jars component (version 15.1.1.0.0). The vulnerability is exploitable over HTTP with no privileges required, allowing attackers to gain unauthorized access to critical data or complete data access, plus limited data modification capabilities. The scope change indicates attacks can cascade to additional products in the environment.

MitigationApply Oracle Critical Patch Updates when available; until then, restrict network access to Coherence HTTP endpoints via firewall or web application firewall, and monitor for indicators of compromise.

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:= 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

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 Oracle Coherence installation
    Search for Coherence installation directories or check for coherence.jar, coherence-wlss-server.jar, or similar Coherence-related JAR files in the system. Common paths include $ORACLE_HOME/coherence, /opt/oracle/coherence, or application lib directories.
    Affected if Oracle Coherence software is present on the system
  2. Determine Coherence version
    Check the version of the installed Oracle Coherence by examining manifest files within coherence.jar, or run: java -jar coherence.jar -version. Also check product documentation or installation logs for version 15.1.1.0.0.
    Affected if Installed version is exactly 15.1.1.0.0
  3. Verify Centralized Third Party Jars component
    Examine Coherence configuration files (tangosol-coherence.xml, coherence-cache-config.xml) for references to CentralizedThirdPartyJars, third-party jar management, or jar-download functionality. Check if the feature is enabled in the Coherence operational configuration.
    Affected if Centralized Third Party Jars component is configured or enabled
  4. Check HTTP endpoint exposure
    Review Coherence HTTP server configuration (typically in tangosol-coherence-override.xml or web-tier config) to identify exposed HTTP listening endpoints. Look for port configurations (often defaults like 20000-20020 range for Coherence*Extend or HTTP servers).
    Affected if Coherence HTTP endpoints are exposed to network access

User is affected if Oracle Coherence version 15.1.1.0.0 is installed AND the Centralized Third Party Jars component is enabled with HTTP network accessibility.

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 Oracle Critical Patch Updates when available; until then, restrict network access to Coherence HTTP endpoints via firewall or web application firewall, and monitor for indicators of compromise.

Fix this in Coherence Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-35306 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