dbcve.org
CoherenceApplication · Oracle

CVE-2026-35304

CRITICAL · 9.8 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: 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 HTTPS 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 confidence

A critical unauthenticated remote code execution vulnerability in Oracle Coherence Core component allows remote attackers to completely takeover the Coherence data grid through specially crafted HTTPS requests. The flaw is easily exploitable with no authentication required and affects versions 12.2.1.4.0 through 15.1.1.0.0.

MitigationApply Oracle Critical Patch Updates for Oracle Coherence or apply vendor-supplied security patches for affected versions immediately; isolate Coherence services from untrusted network segments as an interim measure.

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

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

  1. Identify Oracle Coherence installation and version
    Locate the Oracle Coherence installation directory and check the version file or coherence.jar manifest. Common locations include ORACLE_HOME/coherence or product-specific installation paths. Run 'java -jar coherence.jar -version' if available or check product release documentation.
    Affected if The installed version is 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0, or falls within the range 12.2.1.4.0 through 15.1.1.0.0
  2. Determine if Coherence HTTP server is enabled
    Check if the Coherence HTTP or HTTPS endpoint is configured and running. Review configuration files such as tangosol-coherence.xml, coherence-cache-config.xml, or the HTTP server configuration for port bindings (typically ports 20000-20099 range for Coherence REST). Inspect running processes for Coherence HTTP server listeners.
    Affected if Coherence HTTP/HTTPS server component is actively listening on a network port accessible to the checking system
  3. Verify network exposure of Coherence service
    Identify all network listeners bound to Coherence processes using netstat or similar tools. Determine if the Coherence HTTP port is bound to 0.0.0.0 or an interface accessible from untrusted networks, rather than localhost or protected internal networks.
    Affected if The Coherence HTTP/HTTPS service is exposed on a network interface reachable from untrusted or external networks
  4. Confirm vulnerability applicability
    Review application deployment architecture to confirm the Coherence Core component is in the attack surface. The vulnerability affects the Coherence Core component specifically; check if this component is deployed as part of the Coherence data grid infrastructure.
    Affected if The environment uses Oracle Coherence with the Core component in a configuration that processes HTTP requests

The environment is affected if Oracle Coherence version is 12.2.1.4.0 through 15.1.1.1.0.0 AND the Coherence HTTP server component is enabled and network-accessible.

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 for Oracle Coherence or apply vendor-supplied security patches for affected versions immediately; isolate Coherence services from untrusted network segments as an interim measure.

Fix this in Coherence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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