Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain high-privileged DRM account
-
DeliverySend crafted HTTP request to Access/security component
-
ExploitExploit flaw crossing security scope
-
ExecutionRead all DRM-accessible data and partially modify
-
ImpactImpact linked downstream products
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already hold HIGH privileges (PR:H) on an affected Oracle Hyperion Data Relationship Management 11.2.26.0.000 instance and network HTTP access to its Access and security component. No user interaction is needed (UI:N) and complexity is low (AC:L), but the high-privilege prerequisite is the decisive limiting factor - this is not remotely exploitable by an anonymous attacker. The scope change means successful attacks can reach beyond DRM into additional connected products, so blast radius depends on how DRM is integrated with downstream EPM/finance systems. |
| Impact | This is a well-calibrated 7.6 (High, not Critical), and the CVSS vector is the primary decision driver since every other exploitation signal is absent. The vector AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N shows a network-reachable, low-complexity flaw, but the PR:H requirement is the dominant risk limiter: the attacker must already hold high (administrative) privileges on the Hyperion DRM instance, which sharply narrows the realistic threat population to insiders or an attacker who has already compromised a privileged account. The scope change (S:C) is what pushes the score up - Oracle states attacks 'may significantly impact additional products' - and impact is confidentiality-heavy (C:H = full read of DRM-accessible data) with only partial integrity (I:L) and no availability impact (A:N). No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or imminent exploitation. This is a real but lower-tier priority: patch in the normal Oracle CPU cycle rather than emergency-out-of-band, because the high-privilege precondition makes mass or opportunistic exploitation unlikely. Note the input 'Authentication Bypass' tag directly conflicts with PR:H - this is authenticated, high-privilege access, NOT an auth bypass; treat that tag as erroneous. |
| Exploit ScenarioDerived | An attacker who has already obtained a high-privileged application account (insider, or via prior credential compromise) sends crafted HTTP requests to the Access and security component of Oracle Hyperion Data Relationship Management. Exploitation grants full read of all DRM-accessible master-data plus limited unauthorized modification, and because of the scope change may reach data in connected downstream products. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Oracle Hyperion Data Relationship Management 11.2.26.0.000 lets a high-privileged, network-positioned user defeat the Access and security component and reach well beyond their intended authorization boundary - reading critical master data and gaining update/insert/delete capability over data they should not control. Exploitation is low-complexity (AC:L) and requires no user interaction (UI:N), but it is gated behind a pre-existing high-privilege account on the DRM instance (PR:H), and because the vector carries a scope change (S:C), success can cascade into connected EPM and finance systems that trust DRM as a source of record. No public exploit code or confirmed active exploitation has been identified at time of analysis, and with an EPSS-style signal absent the 7.6 High rating rests almost entirely on the CVSS vector rather than on observed threat activity.
RemediationAI
Patch available per vendor advisory: apply the Oracle Critical Patch Update covering Oracle Hyperion Data Relationship Management at https://www.oracle.com/security-alerts/cspusep2026.html, which is the authoritative source for the applicable fixed build on the 11.2.26.x line - the supplied data does not name an exact patched version number, so confirm the CPU build against your installed 11.2.26.0.000 deployment before treating the finding as closed. Until the fix is in place, the most effective compensating control is to shrink the PR:H precondition that makes this exploitable: audit and reduce every DRM account holding elevated Access and security privileges, enforce least privilege so that only genuinely required administrative identities can reach those functions, and disable or lock dormant privileged accounts - the trade-off is added operational friction for legitimate DRM administrators and possible disruption to scheduled maintenance tasks. In parallel, restrict HTTP access to the DRM web tier to trusted management and integration subnets via firewall or reverse-proxy allowlists, accepting that this may break distributed EPM clients and remote integrators that legitimately call DRM. Because scope change means impact propagates into connected products, review and tighten the trust relationships between DRM and downstream EPM/finance systems, and enable audit logging on privileged DRM operations along with alerting on anomalous reads or bulk hierarchy/data modifications so that abuse of an already-privileged account is at least detectable - detection is a detective control only and does not prevent the disclosure itself.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Oracle Hyperion Data Relationship Management is the master-data-management tier of Oracle's EPM stack, governing hierarchies, dimensions and reference data that downstream consolidation, planning and reporting products consume. The flaw sits in the 'Access and security' component, and Oracle's own tagging labels it an Authentication Bypass, which in practice points to a weakness in how DRM enforces authorization on privileged operations rather than a missing credential check for anonymous users - consistent with the PR:H vector, an attacker must already hold an elevated DRM account. No CWE is disclosed, so the precise defect class (improper authorization, privilege-context confusion, or a broken access-control check on a privileged endpoint) is not confirmable from the available data; what is confirmable is the network/HTTP attack path (AV:N), the low attack complexity, the absence of user interaction, and the scope change (S:C) that lets impact escape the DRM security authority into integrated products. Confidentiality is rated High and Integrity Low, so the dominant risk is bulk disclosure of critical master data, with data-tampering as a secondary but real effect on a subset of records; Availability is explicitly not impacted (A:N), meaning this is a data-exposure and data-integrity problem rather than a denial-of-service one.
Know when Hyperion Data Relationship Management gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
Network HTTP with low complexity, but requires high-privilege access (PR:H); scope change per Oracle, full confidentiality read, only partial integrity, no availability impact.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
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.26.0.000. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. While the vulnerability is in Oracle Hyperion Data Relationship Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hyperion Data Relationship Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Hyperion Data Relationship Management accessible data. CVSS 3.1 Base Score 7.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N).
Executive ViewAI
Oracle Hyperion Data Relationship Management (DRM) 11.2.26.0.000 contains a high-severity authorization weakness that lets a user who already holds an elevated account on the DRM instance step past the product's Access and security controls and read or modify master data outside their assigned scope. Because DRM often serves as the system of record feeding Oracle EPM and downstream finance and reporting platforms, a successful abuse can push unauthorized or corrupted changes into data the business treats as authoritative, creating financial reporting, compliance, and audit exposure. Exploitation requires an existing high-privilege account and no public exploit identified at time of analysis, but with no vendor patch available leadership should treat this as a privileged-access and data-integrity risk rather than an external intrusion risk.
No vendor-released patch identified at time of analysis. Interim mitigations: aggressively reduce and recertify high-privilege accounts on the DRM instance, enforce MFA and just-in-time elevation for administrative access, restrict network access to DRM to trusted management segments only, enable and monitor detailed audit logging of master data read/write activity with alerts on out-of-window changes, reconcile DRM master data against downstream Oracle EPM and finance systems to detect unauthorized modification, and maintain a manual approval and verification step for high-impact master data changes until a vendor patch is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursio
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Lo
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be
This affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2. Rat
Complete takeover of Oracle Hyperion Data Relationship Management 11.2.25.0.000 is possible by remote, unauthenticated a
Full remote takeover of Oracle Hyperion Data Relationship Management 11.2.25.0.000 is possible by an unauthenticated att
Full product takeover of Oracle Hyperion Data Relationship Management 11.2.25.0.000 is achievable by a remote, unauthent
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Rated high severity (CVSS 8.8), th
Full takeover of Oracle Hyperion Data Relationship Management 11.2.25.0.000 is possible when an attacker who already hol
Unauthenticated remote attackers can bypass authentication in Oracle Hyperion Data Relationship Management version 11.2.
Unauthenticated data compromise in Oracle Hyperion Data Relationship Management 11.2.25.0.000 allows a remote attacker t
Unauthorized data compromise in Oracle Hyperion Data Relationship Management 11.2.25.0.000 (Access and security componen
EUVD-2026-79788
GHSA-8p37-3qm7-m2mv
NVD
CVE.org
EPSS
Exploit-DB