Skip to content
major vulnerability· requires attention

Affects widely-used Oracle Coherence in Fusion Middleware; unauthenticated HTTP RCE; CVSS 10.0; high disruption risk.

Infrastructure

CVE-2026-35308

3.1
Low
EPSS 0.47%Patch availableJun 17, 2026

Unauthenticated HTTP RCE in Oracle Coherence; takeover risk.

common questions

Is CVE-2026-35308 being exploited?

Not confirmed. CVE-2026-35308 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-35308?

CVE-2026-35308 is rated Low with a CVSS score of 3.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-35308?

Yes. A fix has been recorded for CVE-2026-35308. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-35308 affect?

CVE-2026-35308 affects Oracle Coherence (Fusion Middleware), Oracle Fusion Middleware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-35308?

Patch promptly when available; restrict HTTP access; monitor.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Coherence (Fusion Middleware)Oracle Fusion Middleware
impact

Unauthenticated remote code execution via HTTP allows takeover; compromises C/I/A of Coherence.

action required

Patch when possible

affected versions
Oracle Corporation Oracle Coherence
  • affected12.2.1.4.0
  • affected14.1.1.0.0
  • affected14.1.2.0.0
  • affected15.1.1.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free