# CVE-2026-61313: Missing authorization in Oracle Hyperion Calculation Manager

> High-privileged attackers can bypass authorization to access and modify critical data in Oracle Hyperion Calculation Manager.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-xmh4-qwvm-fc64

## What is CVE-2026-61313?

CVE-2026-61313 is a medium-severity missing authorization vulnerability in Oracle Hyperion Calculation Manager, 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 Calculation Manager product of Oracle Hyperion (component: Security).   The supported version that is affected is 11.2.25.0.000. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle Hyperion Calculation Manager executes to compromise Oracle Hyperion Calculation Manager.  While the vulnerability is in Oracle Hyperion Calculation Manager, 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 Calculation Manager accessible data as well as  unauthorized update, insert or delete access to some of Oracle Hyperion Calculation Manager accessible data. CVSS 3.1 Base Score 6.7 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Hyperion Calculation Manager.

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

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

## Is CVE-2026-61313 being exploited?

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

## Other vulnerabilities in Oracle Hyperion Calculation Manager

- [CVE-2026-61206](https://insights.sbomify.com/CVE-2026-61206/): Auth bypass in Oracle Hyperion Calculation Manager (critical 9.9)
- [CVE-2026-60858](https://insights.sbomify.com/CVE-2026-60858/): Auth bypass in Oracle Hyperion Calculation Manager (critical 9.8)
- [CVE-2026-62582](https://insights.sbomify.com/CVE-2026-62582/): Missing authorization in Oracle Hyperion Calculation Manager (critical 9.6)
- [CVE-2026-61276](https://insights.sbomify.com/CVE-2026-61276/): Auth bypass in Oracle Hyperion Calculation Manager (high 8.8)
- [CVE-2026-62598](https://insights.sbomify.com/CVE-2026-62598/): Missing authorization in Oracle Hyperion Calculation Manager (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61313 is a medium-severity missing authorization vulnerability in Oracle Hyperion Calculation Manager, 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-61313 in the wild and no public exploit code.

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

## Sources

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

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