Affects Oracle Database Portable Clusterware — widely used enterprise database component; unauthenticated remote exploit enables data tampering and full DoS, high real-world impact.
CVE-2026-71102
Unauthenticated HTTP flaw in Oracle Portable Clusterware enabling data modification and DoS.
Is CVE-2026-71102 being exploited?
Not confirmed. CVE-2026-71102 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.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-71102?
CVE-2026-71102 is rated Critical with a CVSS score of 9.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-71102?
Yes. A fix has been recorded for CVE-2026-71102. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71102 affect?
CVE-2026-71102 affects Oracle Database Portable Clusterware 19.3-19.32, Oracle Database Portable Clusterware 21.3-21.23, Oracle Database Portable Clusterware 23.4.0-23.26.3, Oracle Database Server (Portable Clusterware component). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71102?
Block HTTP access to Clusterware, isolate/segment hosts, deploy WAF, and apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can create/delete/modify Clusterware data and trigger hangs/crashes (complete DoS).
Immediate action required
- affected>= 19.3 and <= 19.32
- affected>= 21.3 and <= 21.23
- affected>= 23.4.0 and <= 23.26.3
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.