PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-87135 Oracle Corporation CVE debrief

A vulnerability in Oracle Hyperion Data Relationship Management, a component of Oracle Hyperion, allows low-privileged attackers with network access via HTTP to compromise the product. This high-severity issue, with a CVSS score of 7.1, can lead to unauthorized access to critical data or complete access to all Oracle Hyperion Data Relationship Management accessible data, as well as unauthorized update, insert, or delete access to some data. The vulnerability is easily exploitable and affects version 11.2.26.0.000 of the product. Defenders should prioritize verifying exposure, restricting network access, and applying remediation to mitigate potential impacts, including data access,

Vendor
Oracle Corporation
Product
Oracle Hyperion Data Relationship Management
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-15
Original CVE updated
2026-09-21
Advisory published
2026-09-15
Advisory updated
2026-09-21

Who should care

Defenders responsible for Oracle Hyperion Data Relationship Management deployments should assess exposure and prioritize remediation, focusing on restricting network access and ensuring up-to-date configurations.

Why it matters

CVE-2026-87135 is a high-severity vulnerability in Oracle Hyperion Data Relationship Management that allows low-privileged attackers with network access to potentially compromise the product, leading to data access and integrity impacts. Defenders should prioritize verifying exposure, restricting access, and applying remediation.

  • Potential unauthorized access to critical data
  • Possible update, insert, or delete access to some data
  • Need for verification of exposure and remediation

Technical summary

The vulnerability in Oracle Hyperion Data Relationship Management, component: Access and security, allows low-privileged attackers with network access via HTTP to compromise the product. Successful attacks can result in unauthorized access to critical data or complete access to all Oracle Hyperion Data Relationship Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Hyperion Data Relationship Management accessible data.

Defensive priority

Defenders should prioritize verifying exposure and applying remediation, focusing on restricting network access and ensuring up-to-date configurations.

Recommended defensive actions

  • Verify and restrict network access to Oracle Hyperion Data Relationship Management
  • Ensure the product is updated to the latest version
  • Monitor for suspicious activity and implement compensating controls if necessary
  • Review and implement asset inventory to track affected systems
  • Plan and execute vendor-supported updates or mitigations through normal change control
  • Conduct exposure review for affected product deployments
  • Track exceptions and retest remediated assets

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impacts, and affected versions. However, specific remediation steps or version fixes require verification from Oracle's official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-87135 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-87135

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-87135 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-87135

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.