Summary
CVE-2026-70870 is a high-severity vulnerability in the Web Client (Unicode) component of Oracle Hyperion Data Relationship Management (DRM). It allows an unauthenticated, remote attacker with network access via HTTP to compromise the application, potentially gaining unauthorized access to critical data or all data accessible to the application, as well as causing a partial denial of service. Oracle rates this vulnerability 8.2 (High) on the CVSS 3.1 scale and disclosed it as part of its August 2026 Critical Patch Update.
Technical details
- Root cause: A flaw in the Web Client’s Unicode-handling component of Oracle Hyperion Data Relationship Management.
- Trigger conditions: The vulnerability is described by Oracle as "easily exploitable," requiring no authentication and no user interaction to trigger.
- Attack vector: Network-based, exploitable over HTTP against the DRM Web Client without valid credentials (AV:N, AC:L, PR:N, UI:N).
- Impact: Successful exploitation can result in unauthorized access to critical data or complete access to all data accessible to Oracle Hyperion Data Relationship Management (high confidentiality impact), and an unauthorized ability to cause a partial denial of service (low availability impact). Integrity is not affected.
Affected software
- Oracle Hyperion Data Relationship Management version 11.2.23.0.000 (the supported version confirmed as affected in the CVE record).
- Oracle’s August 2026 Critical Patch Update also lists other Hyperion Data Relationship Management releases (e.g., 11.2.25.0.000) among impacted products under this update cycle; organizations running any currently supported DRM release should consult the full Oracle risk matrix to confirm applicability to their specific version.
Severity
- CVSS v3.1 Base Score: 8.2 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Mitigation and recommended actions
- Immediate: Apply the Oracle Critical Patch Update for August 2026, which contains the fix for CVE-2026-70870 for Oracle Hyperion Data Relationship Management. Oracle strongly recommends applying CPU fixes as soon as possible.
- If immediate patching is not possible: Restrict network access to the DRM Web Client to trusted internal networks or VPN only, and avoid exposing the Web Client interface directly to the internet until the patch is applied, since the flaw is remotely exploitable without authentication.
- Review Oracle’s official CPU advisory for any product-specific workarounds and confirm the exact patched version applicable to your DRM deployment.

