CVE-2026-35307: Oracle Coherence: unauthenticated RCE, CVSS 10.0

CRITICAL CISA: TRACK*
Published June 17, 2026
CISO Take

Oracle Coherence contains a critical unauthenticated remote code execution vulnerability (CWE-284: Improper Access Control) that allows any network-reachable attacker to fully compromise the server via HTTP with zero credentials or user interaction. The CVSS scope change flag (S:C) means a single exploited Coherence node can cascade into co-located Oracle Fusion Middleware components — a serious blast radius for organizations using Coherence as a caching or session layer in AI/ML pipelines, compounded by 653 downstream dependents in the ecosystem. While the EPSS score of 0.52% (top 60th percentile) indicates active exploitation is not yet widespread and the vulnerability is not in CISA KEV, a CVSS 10.0 profile with no authentication barrier and low complexity will attract rapid weaponization. Apply Oracle's June 2026 Critical Patch Update immediately and, as an interim control, firewall all Coherence HTTP management endpoints from untrusted network segments.

Sources: NVD EPSS OpenSSF ATLAS

What is the risk?

Extremely high risk. CVSS 10.0 with AV:N/AC:L/PR:N/UI:N/S:C is the most severe possible exploit profile — no authentication, no complexity barrier, network-accessible via HTTP with full confidentiality, integrity, and availability impact. For AI deployments using Coherence as a distributed cache (inference results, session state, RAG context stores), full data compromise is achievable. The scope change amplifies exposure beyond Coherence itself to co-located Oracle Middleware components. Low EPSS (0.52%) suggests no public PoC is circulating yet, providing a narrow remediation window before weaponization. OpenSSF scorecard of 5.2/10 indicates sub-optimal supply chain hygiene for the Python client used in AI pipelines.

How does the attack unfold?

Network Scanning
Adversary scans for exposed Oracle Coherence HTTP management or cluster REST endpoints (default ports 7777, 30000) reachable from internet or compromised internal network segment.
AML.T0006
Unauthenticated Exploitation
Attacker sends crafted HTTP request exploiting CWE-284 improper access control, bypassing all authentication and achieving remote code execution on the Coherence server with no credentials required.
AML.T0049
AI Data Exfiltration
With full server access, adversary extracts cached LLM inference results, RAG context documents, session tokens, external LLM API keys, and feature store data held in the Coherence grid.
AML.T0025
Scope Expansion & Persistence
Leveraging the CVSS scope change, attacker pivots to co-located Oracle Fusion Middleware components feeding AI pipelines, achieving broader infrastructure takeover and establishing persistence via legitimate Oracle service accounts.
AML.T0112

What systems are affected?

Package Ecosystem Vulnerable Range Patched
Cohere pip No patch
396 OpenSSF 5.2 296 dependents Pushed 9d ago 13% patched ~14d to patch Full package profile →

Do you use Cohere? You're affected.

How severe is it?

CVSS 3.1
10.0 / 10
EPSS
0.5%
chance of exploitation in 30 days
Higher than 38% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AV AC PR UI S C I A
AV Network
AC Low
PR None
UI None
S Changed
C High
I High
A High

What should I do?

5 steps
  1. PATCH

    Apply Oracle Critical Patch Update June 2026 immediately — oracle.com/security-alerts/cspujun2026.html. Affected: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0.

  2. NETWORK ISOLATION (interim): Firewall all Coherence HTTP/REST management ports (default 7777, 30000) from untrusted segments — Coherence cluster ports must never be internet-facing.

  3. DETECTION

    Monitor for anomalous HTTP requests to Coherence management endpoints, unexpected outbound connections from Coherence JVM processes, and unauthorized data access patterns in grid logs.

  4. AUDIT EXPOSURE

    Enumerate all Coherence instances across environments, especially those serving AI application tiers or acting as RAG context stores.

  5. ROTATE CREDENTIALS

    Post-patch, rotate all credentials, API keys, and session secrets accessible from any Coherence-connected system given the full takeover risk.

What does CISA's SSVC say?

Decision Track*
Exploitation none
Automatable Yes
Technical Impact total

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Article 15 - Accuracy, Robustness and Cybersecurity Article 9 - Risk Management System
ISO 42001
6.1.2 - AI Risk Assessment 8.4 - AI System Security
NIST AI RMF
MANAGE 2.2 - AI Risk Incident Management
OWASP LLM Top 10
LLM05 - Supply Chain Vulnerabilities

Frequently Asked Questions

What is CVE-2026-35307?

Oracle Coherence contains a critical unauthenticated remote code execution vulnerability (CWE-284: Improper Access Control) that allows any network-reachable attacker to fully compromise the server via HTTP with zero credentials or user interaction. The CVSS scope change flag (S:C) means a single exploited Coherence node can cascade into co-located Oracle Fusion Middleware components — a serious blast radius for organizations using Coherence as a caching or session layer in AI/ML pipelines, compounded by 653 downstream dependents in the ecosystem. While the EPSS score of 0.52% (top 60th percentile) indicates active exploitation is not yet widespread and the vulnerability is not in CISA KEV, a CVSS 10.0 profile with no authentication barrier and low complexity will attract rapid weaponization. Apply Oracle's June 2026 Critical Patch Update immediately and, as an interim control, firewall all Coherence HTTP management endpoints from untrusted network segments.

Is CVE-2026-35307 actively exploited?

No confirmed active exploitation of CVE-2026-35307 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-35307?

1. PATCH: Apply Oracle Critical Patch Update June 2026 immediately — oracle.com/security-alerts/cspujun2026.html. Affected: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0. 2. NETWORK ISOLATION (interim): Firewall all Coherence HTTP/REST management ports (default 7777, 30000) from untrusted segments — Coherence cluster ports must never be internet-facing. 3. DETECTION: Monitor for anomalous HTTP requests to Coherence management endpoints, unexpected outbound connections from Coherence JVM processes, and unauthorized data access patterns in grid logs. 4. AUDIT EXPOSURE: Enumerate all Coherence instances across environments, especially those serving AI application tiers or acting as RAG context stores. 5. ROTATE CREDENTIALS: Post-patch, rotate all credentials, API keys, and session secrets accessible from any Coherence-connected system given the full takeover risk.

What systems are affected by CVE-2026-35307?

This vulnerability affects the following AI/ML architecture patterns: AI-enabled enterprise applications on Oracle Fusion Middleware, Distributed caching layers for LLM inference results, RAG pipelines using Oracle middleware for context storage, Session management backends for AI-powered web applications, Feature stores backed by Oracle Coherence data grids.

What is the CVSS score for CVE-2026-35307?

CVE-2026-35307 has a CVSS v3.1 base score of 10.0 (CRITICAL). The EPSS exploitation probability is 0.47%.

What is the AI security impact?

Affected AI Architectures

AI-enabled enterprise applications on Oracle Fusion MiddlewareDistributed caching layers for LLM inference resultsRAG pipelines using Oracle middleware for context storageSession management backends for AI-powered web applicationsFeature stores backed by Oracle Coherence data grids

MITRE ATLAS Techniques

AML.T0006 Active Scanning
AML.T0025 Exfiltration via Cyber Means
AML.T0049 Exploit Public-Facing Application
AML.T0112 Machine Compromise

Compliance Controls Affected

EU AI Act: Article 15, Article 9
ISO 42001: 6.1.2, 8.4
NIST AI RMF: MANAGE 2.2
OWASP LLM Top 10: LLM05

What are the technical details?

Original Advisory

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 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).

Exploitation Scenario

An adversary scanning enterprise Oracle environments identifies a Coherence HTTP management interface exposed on an internal network segment accessible after VPN compromise or insider access. Without any credentials, they send a crafted HTTP request exploiting the CWE-284 access control flaw, achieving arbitrary code execution on the Coherence node backing an enterprise AI model-serving platform. From this foothold they extract the full inference result cache — including proprietary LLM outputs and RAG context documents — alongside API keys for external LLM providers stored in application configuration. Exploiting the CVSS scope change, they pivot laterally to the co-located Oracle WebLogic server hosting the AI application logic, ultimately compromising the entire AI pipeline, exfiltrating training datasets, and establishing persistence via legitimate Oracle service accounts.

Weaknesses (CWE)

CWE-284 — Improper Access Control: The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

  • [Architecture and Design, Operation] Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • [Architecture and Design] Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Source: MITRE CWE corpus.

CVSS Vector

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

Timeline

Published
June 17, 2026
Last Modified
June 19, 2026
First Seen
June 17, 2026

Related Vulnerabilities