CVE-2026-70872 Overview
CVE-2026-70872 is a critical vulnerability in the Oracle Hyperion Data Relationship Management product, specifically within the Access and security component. The flaw affects supported version 11.2.25.0.000 and is exploitable by an unauthenticated attacker with network access over HTTP.
Successful exploitation allows attackers to gain unauthorized read, create, delete, or modify access to critical data managed by Oracle Hyperion Data Relationship Management. The vulnerability affects both confidentiality and integrity of enterprise master data workflows commonly used for financial consolidation and reporting.
Critical Impact
An unauthenticated network attacker can compromise the confidentiality and integrity of all data accessible through Oracle Hyperion Data Relationship Management.
Affected Products
- Oracle Hyperion Data Relationship Management version 11.2.25.0.000
- Component: Access and security
- Oracle Hyperion product family
Discovery Timeline
- 2026-08-18 - CVE-2026-70872 published to NVD
- 2026-08-18 - Oracle publishes Security Alert August 2026
- 2026-08-20 - Last updated in NVD database
Technical Details for CVE-2026-70872
Vulnerability Analysis
The vulnerability resides in the Access and security component of Oracle Hyperion Data Relationship Management (DRM). DRM manages enterprise master data hierarchies used for financial consolidation, reporting, and analytics. A weakness in how the component enforces access controls allows an unauthenticated remote attacker to interact with protected data operations.
Because DRM often serves as an authoritative source for chart-of-accounts, cost centers, and organizational hierarchies, unauthorized modifications can cascade into downstream Enterprise Performance Management (EPM) systems. The attack surface is exposed over HTTP, meaning any network path to the DRM web tier is sufficient for exploitation.
Root Cause
Oracle's advisory categorizes the issue under Access and security, indicating a broken access control or authentication bypass condition. The component fails to properly validate the identity or authorization of the requester before performing sensitive operations on managed data. Oracle has not published deeper technical specifics per its standard disclosure practice.
Attack Vector
The attacker sends crafted HTTP requests to the DRM application over the network. No credentials, user interaction, or elevated privileges are required. The low attack complexity and network reachability make exploitation practical against any internet-exposed or laterally reachable DRM instance.
Refer to the Oracle Security Alert August 2026 for vendor-provided details. No public proof-of-concept has been observed, and the current EPSS probability is 0.325% (25.45th percentile).
Detection Methods for CVE-2026-70872
Indicators of Compromise
- Unexpected HTTP requests to Oracle Hyperion DRM endpoints from unauthenticated sources or unusual IP ranges.
- Unauthorized creation, deletion, or modification events in DRM audit logs, especially outside change-management windows.
- Anomalous access to master data hierarchies, node properties, or export operations without corresponding authenticated sessions.
- Downstream EPM systems ingesting hierarchy changes that were not approved through standard workflows.
Detection Strategies
- Enable and review DRM application audit logging for all data modification and export actions, correlating with authenticated session identifiers.
- Monitor the DRM web tier for HTTP request patterns that bypass login flows or access API endpoints without prior authentication tokens.
- Baseline normal administrative activity and alert on deviations in request volume, source geography, or off-hours access.
Monitoring Recommendations
- Forward DRM web server, application, and audit logs to a centralized SIEM or data lake for correlation with identity and network telemetry.
- Alert on failed authorization events followed by successful data operations from the same source.
- Track integrity of exported master data files against known-good baselines to identify unauthorized modifications.
How to Mitigate CVE-2026-70872
Immediate Actions Required
- Apply the fixes referenced in the Oracle Security Alert August 2026 to all Oracle Hyperion Data Relationship Management deployments running version 11.2.25.0.000.
- Restrict network access to the DRM web tier to trusted administrative networks and VPN segments only.
- Audit DRM user accounts, roles, and recent data modifications for signs of unauthorized changes.
- Rotate service credentials and API keys used by integrations with DRM after patching.
Patch Information
Oracle addressed CVE-2026-70872 in the August 2026 Security Alert. Administrators should review the Oracle Security Alert August 2026 for the exact patch bundle applicable to Oracle Hyperion Data Relationship Management 11.2.25.0.000 and follow Oracle's documented upgrade procedures.
Workarounds
- Place DRM behind a reverse proxy or web application firewall that enforces authentication before requests reach the application tier.
- Disable or firewall off any DRM HTTP endpoints that are not required for business operations.
- Enforce network-layer access control lists limiting DRM connectivity to known EPM integration hosts and administrator workstations.
# Example: restrict DRM web tier access using host-based firewall (Windows)
netsh advfirewall firewall add rule name="Restrict DRM HTTP" ^
dir=in action=block protocol=TCP localport=80,443 ^
remoteip=any
netsh advfirewall firewall add rule name="Allow DRM Admin Subnet" ^
dir=in action=allow protocol=TCP localport=80,443 ^
remoteip=10.10.20.0/24
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

