CVE-2026-70872: Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Ac...
Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and security). The supported version that is affected is 11.2.25.0.000. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Data Relationship Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Hyperion Data Relationship Management accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
Security readout for executives and security teams
Plain-English summary
An unauthenticated network attacker could read, create, delete, or change critical data in an affected Oracle Hyperion Data Relationship Management deployment. The flaw threatens confidentiality and integrity, potentially undermining trusted business data without requiring a user to take any action.
Executive priority
Treat affected, reachable deployments as an urgent remediation priority. The principal business risk is silent theft or manipulation of critical relationship-management data. Prioritize containment and vendor guidance review immediately, while avoiding claims of an active campaign without supporting evidence.
Technical view
CVE-2026-70872 is an access-control vulnerability (CWE-284) affecting Oracle Hyperion Data Relationship Management 11.2.25.0.000. It is remotely exploitable through HTTP with low complexity, no privileges, and no user interaction. The CVSS 3.1 score is 9.1; confidentiality and integrity impacts are high, while availability impact is rated none.
Likely exposure
Exposure is established for version 11.2.25.0.000. Risk is greatest where the application’s HTTP service is reachable from untrusted or broadly accessible networks. The bundle does not identify other affected versions or deployment prerequisites, so organizations should verify their exact installed version and network paths.
Exploitation context
The vulnerability is described as easily exploitable and does not require authentication or user interaction. However, the source bundle marks it absent from KEV and provides no evidence of active exploitation, public exploit availability, or observed attacks.
Researcher notes
The supplied vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, consistent with a remotely reachable access-control failure. Public details in the bundle do not identify the vulnerable endpoint, underlying mechanism, patch identifier, exploit artifacts, or detection signatures. Validation should remain non-invasive and configuration-focused.
Mitigation direction
Review Oracle’s advisory for the vendor-prescribed update or mitigation.
Prioritize affected systems because unauthorized access could compromise all application-accessible data.
Restrict HTTP access to trusted networks and authorized administrative paths until vendor remediation is confirmed.
Back up critical DRM data and protect backups from modification.
Increase monitoring for unexpected access and critical data changes.
Validation and detection
Inventory Oracle Hyperion DRM deployments and confirm their exact versions.
Identify whether version 11.2.25.0.000 is reachable over HTTP from untrusted networks.
Confirm Oracle-prescribed remediation is applied using approved configuration or patch records.
Review access and audit logs for unexplained reads, creations, deletions, or modifications.
Verify network controls limit HTTP access to intended trusted sources.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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.