# CVE-2026-70921: Missing authorization in Oracle Hyperion Financial Management

> Unauthenticated attackers can read, create, delete, or modify critical data in Oracle Hyperion Financial Management via network access.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 22 Aug 2026
- **Also known as:** GHSA-7xwm-xp2c-m44w

## What is CVE-2026-70921?

CVE-2026-70921 is a critical missing authorization vulnerability in Oracle Hyperion Financial Management, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Hyperion Financial Management product of Oracle Hyperion (component: Security).   The supported version that is affected is 11.2.25.0.000. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Hyperion Financial Management.  While the vulnerability is in Oracle Hyperion Financial Management, attacks may significantly impact additional products (scope change).  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 data. CVSS 3.1 Base Score 10.0 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Hyperion Financial Management.

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

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

## Is CVE-2026-70921 being exploited?

There is no known exploitation of CVE-2026-70921 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Hyperion Financial Management

- [CVE-2026-87230](https://insights.sbomify.com/CVE-2026-87230/): Missing authorization in Oracle Hyperion Financial Management (critical 10.0)
- [CVE-2012-1714](https://insights.sbomify.com/CVE-2012-1714/): Code injection in n/a (critical 10.0)
- [CVE-2026-87172](https://insights.sbomify.com/CVE-2026-87172/): Privilege escalation in Oracle Hyperion Financial Management (critical 9.9)
- [CVE-2026-70920](https://insights.sbomify.com/CVE-2026-70920/): Auth bypass in Oracle Hyperion Financial Management (critical 9.9)
- [CVE-2026-87184](https://insights.sbomify.com/CVE-2026-87184/): SQL injection in Oracle Hyperion Financial Management (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70921 and fix it if it is affected.

What it is: CVE-2026-70921 is a critical missing authorization vulnerability in Oracle Hyperion Financial Management, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70921 in the wild and no public exploit code.

Affected product: Oracle Hyperion Financial 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-70921/ (Markdown: https://insights.sbomify.com/CVE-2026-70921/index.md)
```

## Sources

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

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