Description

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 low privileged 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 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.1",
  "pubDate": "2026-08-18T21:17:44.610Z",
  "pubdate": "2026-08-18T21:17:44.610Z",
  "executiveSummary": "A security vulnerability has been identified within the Oracle Hyperion Data Relationship Management product, specifically affecting the Access and security component in version 11.2.25.0.000. This vulnerability allows a low-privileged authenticated attacker with network access via the HTTP protocol to compromise the confidentiality and integrity of the application. Successful exploitation of this flaw requires low complexity and does not require user interaction, enabling malicious actors to perform unauthorized creation, deletion, or modification of critical data, as well as gain unauthorized access to all accessible data within the Oracle Hyperion Data Relationship Management system. The vulnerability carries a CVSS 3.1 Base Score of 8.1 with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, highlighting significant risks to data integrity and confidentiality. Organizations operating the affected version face severe operational and compliance risks if unauthorized modifications or data exfiltration occur, necessitating immediate defensive measures and adherence to vendor-supplied security patches.",
  "technicalDetails": "The vulnerability resides in the Access and security component of Oracle Hyperion Data Relationship Management version 11.2.25.0.000. The root cause stems from insufficient access controls and privilege enforcement mechanisms within the application's request handling architecture, specifically concerning HTTP-based interactions. The attack vector is entirely network-accessible via the HTTP protocol, allowing remote threat actors to reach the vulnerable service without physical proximity or local shell access.\nExploitation requires an attacker to possess low-level privileges within the system, meaning the adversary must first authenticate with standard user credentials. Once authenticated, the attacker crafts specialized HTTP requests targeting the vulnerable Access and security component. Because the application fails to adequately validate whether the requesting security context possesses the requisite administrative or operational authorization for specific data manipulation functions, the request is processed and executed by the backend logic.\nThe step-by-step attack flow proceeds as follows: First, the low-privileged attacker establishes a network connection to the Oracle Hyperion Data Relationship Management service over HTTP. Second, the attacker submits crafted requests designed to target sensitive hierarchical data or security configurations managed by the application. Third, the Access and security component improperly authorizes the payload, bypassing expected privilege checks. Finally, the system executes the requested operations, resulting in unauthorized data creation, deletion, modification, or exposure.\nThe post-exploitation impact includes severe compromise of data confidentiality and integrity. Attackers can exfiltrate critical master data, metadata, and structural hierarchies, or maliciously alter and delete records across the Oracle Hyperion Data Relationship Management environment. The scope remains unchanged (S:U), but the high impact on both confidentiality (C:H) and integrity (I:H) demonstrates a critical failure in authorization enforcement, while availability (A:N) remains unaffected by this specific vector."
}