Summary
CVE-2026-70749 is a high-severity vulnerability in the Server component of Oracle Hyperion Financial Reporting that allows an unauthenticated, remote attacker with network access via HTTP to compromise the application. Oracle’s own advisory language classifies this as "difficult to exploit," but warns that successful exploitation "can result in takeover of Oracle Hyperion Financial Reporting" — impacting confidentiality, integrity, and availability. The vulnerability was published as part of Oracle’s Critical Security Patch Update (CSPU) released on August 18, 2026.
Technical details
- Root cause: Oracle has not published a detailed root-cause description or CWE classification in the public CVE record; the vendor advisory characterizes it only as a flaw in the Server component of the product.
- Trigger conditions: The vulnerability is reachable over HTTP without any authentication and does not require user interaction, but Oracle rates the attack complexity as High (AC:H), indicating exploitation requires specific conditions or non-trivial attacker effort to succeed reliably.
- Attack vector: Network-based (AV:N) — no local access, credentials, or victim interaction are required for an attacker to reach the vulnerable component.
- Impact: Successful exploitation results in complete takeover of the affected Hyperion Financial Reporting instance, with full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).
Affected software
- Oracle Hyperion Financial Reporting — version 11.2.25.0.000 (Server component)
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Apply the fix provided in Oracle’s Critical Security Patch Update dated August 18, 2026, which addresses CVE-2026-70749 for Oracle Hyperion Financial Reporting 11.2.25.0.000. Organizations should consult Oracle’s advisory directly for the specific patch identifier applicable to their environment and apply it as soon as possible given the network-exploitable, unauthenticated nature of the flaw.
- If immediate patching is not possible: Restrict network exposure of Hyperion Financial Reporting management and application interfaces — do not expose the service directly to the internet, and limit HTTP access to trusted internal networks or via a VPN/reverse proxy with strict access controls. Monitor HTTP access logs for anomalous or unauthenticated requests to the Financial Reporting server component until the patch can be applied.

