# CVE-2026-87132: Cross-site request forgery in Oracle Hyperion Data Relationship Management > A CSRF vulnerability in Oracle Hyperion DRM allows attackers to access and modify data via HTTP with user interaction. - **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 15 Sep 2026 - **Updated:** 21 Sep 2026 - **Also known as:** GHSA-rf8p-cwv3-44x7 ## What is CVE-2026-87132? CVE-2026-87132 is a high-severity vulnerability in Oracle Hyperion Data Relationship Management, published on 15 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and security). The supported version that is affected is 11.2.26.0.000. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Hyperion Data Relationship Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability 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. CVSS 3.1 Base Score 7.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N). Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2026-87132? It affects 1 product. Products: Oracle Hyperion Data Relationship Management. ## How do I fix CVE-2026-87132? No fix has been published for CVE-2026-87132 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-87132 being exploited? There is no known exploitation of CVE-2026-87132 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Hyperion Data Relationship Management - [CVE-2026-70880](https://insights.sbomify.com/CVE-2026-70880/): Auth bypass in Oracle Hyperion Data Relationship Management (critical 10.0) - [CVE-2026-70871](https://insights.sbomify.com/CVE-2026-70871/): Auth bypass in Oracle Hyperion Data Relationship Management (critical 9.8) - [CVE-2026-70873](https://insights.sbomify.com/CVE-2026-70873/): Auth bypass in Oracle Hyperion Data Relationship Management (critical 9.8) - [CVE-2026-87128](https://insights.sbomify.com/CVE-2026-87128/): Missing authorization in Oracle Hyperion Data Relationship Management (critical 9.1) - [CVE-2026-87129](https://insights.sbomify.com/CVE-2026-87129/): Missing authorization in Oracle Hyperion Data Relationship Management (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-87132 and fix it if it is affected. What it is: CVE-2026-87132 is a high-severity vulnerability in Oracle Hyperion Data Relationship Management, published on 15 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-87132 in the wild and no public exploit code. Affected product: Oracle Hyperion Data Relationship Management. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-87132/ (Markdown: https://insights.sbomify.com/CVE-2026-87132/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-87132 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-87132 - OSV: https://osv.dev/vulnerability/CVE-2026-87132 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-87132/ Summaries are generated and may contain mistakes; the official description above is the record.