# CVE-2026-70879: Privilege escalation in Oracle Hyperion Data Relationship Management

> A low-privileged attacker with local access can escalate privileges to take over Oracle Hyperion Data Relationship Management, impacting confidentiality, integrity, and availability.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-m3wv-43p8-ghhj

## What is CVE-2026-70879?

CVE-2026-70879 is a high-severity vulnerability in Oracle Hyperion Data Relationship Management, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.25.0.000. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Hyperion Data Relationship Management executes to compromise Oracle Hyperion Data Relationship Management.  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 takeover of Oracle Hyperion Data Relationship Management. CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-70879?

It affects 1 product.


Products: Oracle Hyperion Data Relationship Management.

## How do I fix CVE-2026-70879?

No fix has been published for CVE-2026-70879 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70879 being exploited?

There is no known exploitation of CVE-2026-70879 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-70879 and fix it if it is affected.

What it is: CVE-2026-70879 is a high-severity vulnerability in Oracle Hyperion Data Relationship Management, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70879 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-70879/ (Markdown: https://insights.sbomify.com/CVE-2026-70879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70879
- OSV: https://osv.dev/vulnerability/CVE-2026-70879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70879/
Summaries are generated and may contain mistakes; the official description above is the record.