CVE-2026-71102: Vulnerability in the Portable Clusterware component of Oracle Database Server.
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).
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker who can reach an affected Oracle Database Server’s Portable Clusterware HTTP interface could alter or delete critical data and repeatedly crash the component. No confidentiality impact is identified, but integrity and service availability risks are severe.
Executive priority
Treat this as an immediate remediation priority for reachable affected systems. The combination of unauthenticated network access, critical-data modification, and complete denial of service could disrupt database operations. Prioritize internet-facing or broadly reachable environments, then validate internal exposure and remediation coverage.
Technical view
CVE-2026-71102 is a CWE-284 access-control vulnerability in Oracle Database Server Portable Clusterware. It is remotely exploitable over HTTP without privileges or user interaction. Affected releases are 19.3–19.32, 21.3–21.23, and 23.4.0–23.26.3. CVSS 3.1 is 9.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.
Likely exposure
Exposure is highest where affected Portable Clusterware HTTP services are reachable from untrusted or broadly accessible networks. Systems outside the listed version ranges are not identified as affected by the supplied evidence. Component deployment and actual HTTP reachability must be verified locally.
Exploitation context
The vulnerability is described as easily exploitable, requiring only network access over HTTP, without authentication or user interaction. The source bundle marks it absent from KEV and provides no evidence of active exploitation, public exploit availability, or observed attacks. KEV absence does not prove exploitation is not occurring.
Researcher notes
The supplied record establishes access-control weakness, HTTP attack vector, affected ranges, and high integrity and availability impact. It does not identify the vulnerable endpoint, root cause, indicators of compromise, exploit maturity, or a specific patch or workaround. Testing should remain non-destructive and follow Oracle guidance.
Mitigation direction
Review Oracle’s advisory and follow its remediation guidance for every affected deployment.
Apply vendor-provided security updates when Oracle confirms the applicable update for each installed release.
Restrict Portable Clusterware HTTP access to explicitly authorized management networks and systems.
Use network controls to block untrusted access while remediation is validated.
Maintain reliable backups and recovery procedures for critical Portable Clusterware-accessible data.
Validation and detection
Inventory Oracle Database Server deployments and compare Portable Clusterware versions with the affected ranges.
Identify every network path capable of reaching Portable Clusterware over HTTP.
Verify access controls limit HTTP connectivity to authorized management sources.
Confirm vendor-recommended remediation is installed and recorded for each affected system.
Review monitoring for unexpected data changes, hangs, repeated crashes, or unauthorized HTTP activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.