PatchSiren cyber security CVE debrief
CVE-2026-87190 Oracle CVE debrief
A vulnerability in Oracle Hyperion Financial Management allows a low-privileged attacker with network access via HTTP to potentially compromise the product. Successful attacks can result in a takeover of Oracle Hyperion Financial Management. The vulnerability has a CVSS score of 7.5 and can be exploited by a low-privileged attacker with network access via HTTP. Defenders should prioritize verifying exposure and applying remediation to prevent potential takeover and compromise of Oracle Hyperion Financial Management.
- Vendor
- Oracle
- Product
- Hyperion Financial Management
- CVSS
- HIGH 7.5
- 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
Defenders responsible for Oracle Hyperion Financial Management deployments should assess exposure and prioritize remediation. Defenders should prioritize verifying exposure and applying remediation to prevent potential takeover and compromise of Oracle Hyperion Financial Management.
Why it matters
Defenders should prioritize verifying exposure and applying remediation to prevent potential takeover and compromise of Oracle Hyperion Financial Management.
- Potential takeover of Oracle Hyperion Financial Management
- Compromise of confidentiality, integrity, and availability
Technical summary
The vulnerability in Oracle Hyperion Financial Management has a CVSS score of 7.5 and can be exploited by a low-privileged attacker with network access via HTTP. The vulnerability affects Oracle Hyperion Financial Management version 11.2.26.0.000. Successful attacks of this vulnerability can result in takeover of Oracle Hyperion Financial Management. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The supported version that is affected is 11.2.26.0.000.
Defensive priority
Defenders should prioritize verifying exposure and applying remediation, focusing on restricting network access and ensuring proper authentication.
Recommended defensive actions
- Verify and restrict network access to Oracle Hyperion Financial Management
- Ensure proper authentication and authorization
- Apply vendor-provided remediation
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD detail page provide information on the vulnerability, including its CVSS score and vector. The vulnerability affects Oracle Hyperion Financial Management version 11.2.26.0.000. The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hyperion Financial Management. The CVE record was published on 2026-09-15T20:19:06.957Z and has not been modified since then.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-87190 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-87190
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-87190 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-87190
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.