Summary
CVE-2026-87170 is a critical vulnerability in the Security component of Oracle Hyperion Financial Management. It allows an unauthenticated, remote attacker with only network access via HTTP to compromise the application, resulting in unauthorized creation, deletion, or modification of data as well as unauthorized read access to all data accessible to the application. Oracle rates this issue 9.1 (Critical) on the CVSS v3.1 scale, and it was disclosed as part of Oracle’s September 2026 Critical Patch Update.
Technical details
- Root cause: A flaw in the Security component of Oracle Hyperion Financial Management that fails to properly enforce authentication/authorization controls on requests reaching the application over HTTP.
- Trigger conditions: No authentication or user interaction is required; the attacker only needs network access to the HTTP interface exposed by the affected Hyperion Financial Management deployment.
- Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N) — consistent with an easily exploitable, remotely reachable flaw.
- Impact: High confidentiality impact and high integrity impact, with no availability impact (C:H/I:H/A:N). Successful exploitation can let an attacker create, delete, or modify data, and read all data accessible to the application, without needing valid credentials.
Affected software
- Oracle Hyperion Financial Management, version 11.2.26.0.000
Severity
- CVSS v3.1 Base Score: 9.1 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate: Apply the Oracle Critical Patch Update for September 2026, which addresses CVE-2026-87170 for Oracle Hyperion Financial Management 11.2.26.0.000. Organizations should update to the version specified by Oracle in the September 2026 Critical Patch Update advisory as soon as possible.
- If immediate patching is not possible: Restrict network access to the Hyperion Financial Management HTTP interface to trusted internal networks or VPN-only access, and monitor for anomalous unauthenticated requests to the application until the patch can be applied. Oracle states that patches for this vulnerability must be applied through the Critical Patch Update process; workarounds outside of patching are not provided by the vendor.

