CVE-2026-87235 Oracle Corporation CVE debrief

Who should care

Defenders responsible for Oracle Hyperion Financial Management deployments should assess exposure and potential impacts. This includes operators, security teams, and vulnerability management teams who need to verify exposure, assess potential data integrity and confidentiality impacts, and implement compensating controls for unauthorized access.

Why it matters

Defenders should prioritize verifying exposure and assessing potential data integrity and confidentiality impacts due to a difficult-to-exploit vulnerability in Oracle Hyperion Financial Management.

• Potential unauthorized data modification or deletion
• Possible unauthorized access to critical data
• Need for verification of affected versions and exposure
• Potential data integrity and confidentiality impacts

Technical summary

A difficult-to-exploit vulnerability in Oracle Hyperion Financial Management (component: Security) allows unauthenticated attackers with network access via SSH to compromise the system, potentially leading to unauthorized creation, deletion, or modification of critical data. The vulnerability has a CVSS score of 7.4 and is considered high severity. CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Financial Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Hyperion Financial Management accessible

Defensive priority

Defenders should prioritize verifying exposure and assessing potential data integrity and confidentiality impacts.

Recommended defensive actions

• Verify exposure of Oracle Hyperion Financial Management version 11.2.26.0.000 to this vulnerability
• Assess potential data integrity and confidentiality impacts
• Review and implement compensating controls for unauthorized access
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Oracle Hyperion Financial Management. However, the scope of affected versions and potential exploitation remains limited. The vulnerability has a CVSS score of 7.4 and is considered high severity. Defenders should verify exposure and assess potential impacts. The CVE record and NVD entry provide further details.

Sources and references

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.