cve.bz

CVE-2026-71102 oracle database server: Improper Access Control

9.1 criticalEPSS 0.4%

Critical (9.1) in oracle database server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Vulnerability in the Portable Clusterware component of Oracle Database Server. Supported versions that are affected are 19.3-19.32, 21.3-21.23 and 23.4.0-23.26.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Portable Clusterware. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Portable Clusterware accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Portable Clusterware. CVSS 3.1 Base Score 9.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-71102 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71102?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71102?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71102 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-71102

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-71102](https://cve.bz/cve/badge/CVE-2026-71102.svg)](https://cve.bz/cve/CVE-2026-71102)

HTML:

<a href="https://cve.bz/cve/CVE-2026-71102"><img src="https://cve.bz/cve/badge/CVE-2026-71102.svg" alt="CVE-2026-71102"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Oracle Corporation Oracle Database Serverfrom 19.3 through 19.32
Oracle Corporation Oracle Database Serverfrom 21.3 through 21.23
Oracle Corporation Oracle Database Serverfrom 23.4.0 through 23.26.3

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON