Summary
CVE-2026-70952 is a high-severity vulnerability in the Security component of Oracle Hyperion Financial Management. The flaw is remotely exploitable over HTTP by an unauthenticated attacker and requires no user interaction, allowing unauthorized access to sensitive financial data along with a partial denial-of-service impact. Oracle disclosed the issue as part of its August 2026 Critical Security Patch Update, assigning it a CVSS v3.1 base score of 8.2 (High).
Technical details
- Root cause: A flaw in the Security component of Oracle Hyperion Financial Management that fails to properly enforce access controls, permitting unauthorized retrieval of data handled by the application.
- Trigger conditions: No authentication or user interaction is required; the vulnerability can be triggered by an attacker who has network access to the application over HTTP.
- Attack vector: Network (AV:N) — exploitable remotely without prior authentication (PR:N) and without any user interaction (UI:N); attack complexity is low (AC:L).
- Impact: Confidentiality impact is High — successful exploitation can result in unauthorized access to critical data or complete access to all data accessible to Oracle Hyperion Financial Management. Availability impact is Low, indicating partial denial-of-service potential. Integrity is not affected.
Affected software
- Oracle Hyperion Financial Management, version 11.2.25.0.000
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 official Oracle security patch for Oracle Hyperion Financial Management released in the August 2026 Critical Security Patch Update. Organizations running version 11.2.25.0.000 should prioritize patching given the unauthenticated, network-exploitable nature of this flaw.
- If immediate patching is not possible: Restrict network exposure of Oracle Hyperion Financial Management by limiting access to trusted internal networks or VPN-only access, and place the application behind a web application firewall or reverse proxy to monitor and restrict anomalous HTTP requests until the patch can be applied.
- Review Oracle’s official advisory for the complete list of affected components and any additional configuration-based mitigations before and after patching.

