PatchSiren cyber security CVE debrief
CVE-2026-87172 Oracle CVE debrief
A critical vulnerability exists in Oracle Hyperion Financial Management 11.2.26.0.000. Low-privileged attackers with network access via HTTP can easily exploit this vulnerability, potentially leading to a takeover of the affected system. The vulnerability allows attackers to compromise the system, impacting confidentiality, integrity, and availability. Security teams must assess exposure and apply necessary patches or mitigations to prevent potential system takeover and data compromise.
- Vendor
- Oracle
- Product
- Hyperion Financial Management
- CVSS
- CRITICAL 9.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-15
- Original CVE updated
- 2026-09-22
- Advisory published
- 2026-09-15
- Advisory updated
- 2026-09-22
Who should care
Security teams, IT administrators, and financial management teams responsible for Oracle Hyperion Financial Management should assess exposure and apply necessary patches or mitigations.
Why it matters
A critical vulnerability in Oracle Hyperion Financial Management requires immediate attention to assess exposure and apply necessary patches or mitigations to prevent potential system takeover and data compromise.
- Potential system takeover by low-privileged attackers
- Compromise of confidentiality, integrity, and availability
- Scope change impacting additional products
- Verification of patch application and system security
Technical summary
The vulnerability in Oracle Hyperion Financial Management 11.2.26.0.000 allows low-privileged attackers with network access via HTTP to compromise the system, potentially leading to a takeover. The CVSS 3.1 Base Score is 9.9, indicating a critical vulnerability. The vulnerability impacts confidentiality, integrity, and availability, and security teams must assess exposure and apply necessary patches or mitigations to prevent potential system takeover and data compromise. The affected version is 11.2.26.0.000, and the vulnerability is exploitable via HTTP.
Defensive priority
Immediate attention is required to assess exposure and apply necessary patches or mitigations.
Recommended defensive actions
- Assess exposure of Oracle Hyperion Financial Management 11.2.26.0.000 in your environment.
- Apply necessary patches or mitigations as recommended by Oracle.
- Monitor network access and privileges to prevent exploitation.
- Review and update incident response plans to address potential impacts.
- Verify patch application and system security.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD detail page provide information on the vulnerability, its impact, and affected versions. The vulnerability has a CVSS 3.1 Base Score of 9.9, indicating a critical vulnerability. There are no known exploits, but defenders should verify patch application and system security. The affected version is 11.2.26.0.000, and the vulnerability is exploitable via HTTP.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-87172 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-87172
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-87172 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-87172
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cspusep2026.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.