Summary
CVE-2026-70880 is a critical, easily exploitable vulnerability in the Access and security component of Oracle Hyperion Data Relationship Management (DRM) that allows a completely unauthenticated, remote attacker with network access via TCP to fully compromise the affected system. Oracle disclosed the flaw in its August 2026 Critical Security Patch Update, and it carries the maximum CVSS v3.1 base score of 10.0 due to the combination of no authentication requirement, no user interaction, a changed scope, and complete loss of confidentiality, integrity, and availability.
Technical details
- Root cause: A flaw in the Access and security component of Hyperion DRM that fails to properly enforce access controls, allowing an attacker to bypass authentication entirely.
- Trigger conditions: No credentials or user interaction are required; the attacker only needs network (TCP) connectivity to a vulnerable DRM instance.
- Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
- Scope: Changed (S:C) — successful exploitation can impact resources beyond the vulnerable component itself, potentially affecting other Oracle products/components that share the compromised environment.
- Impact: Complete takeover of Oracle Hyperion DRM, with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H) — attackers can read, modify, or destroy data and disrupt service.
Affected software
- Oracle Hyperion Data Relationship Management version 11.2.25.0.0
- Oracle Hyperion Data Relationship Management version 11.2.23.0.0
- (Confirm exact patch applicability for your deployed release against Oracle’s August 2026 Critical Security Patch Update risk matrix)
Severity
- CVSS v3.1 Base Score: 10.0 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Apply the Oracle August 2026 Critical Security Patch Update (CSPU) fix for Oracle Hyperion Data Relationship Management. Organizations should upgrade to the patched release identified in Oracle’s advisory for the 11.2.25.0.0 (and 11.2.23.0.0) DRM code lines as soon as possible.
- If patching cannot be performed immediately:
- Remove direct internet exposure of Hyperion DRM management/administration interfaces; restrict access to trusted internal networks only.
- Place the application behind a properly configured firewall, VPN, or access-control proxy that enforces authentication before requests reach the DRM service.
- Monitor DRM server logs and network traffic for anomalous, unauthenticated administrative or configuration-changing requests.
- Given the CVSS 10.0 score and unauthenticated network exploitability, treat any internet-facing DRM instance as high risk until patched.

