# CVE-2026-62558: Missing authorization in Oracle Hyperion Infrastructure Technology

> An attacker with local access can compromise Oracle Hyperion Infrastructure Technology to read or modify critical data, requiring user interaction.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-g445-wcv9-wg79

## What is CVE-2026-62558?

CVE-2026-62558 is a medium-severity missing authorization vulnerability in Oracle Hyperion Infrastructure Technology, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Hyperion Infrastructure Technology product of Oracle Hyperion (component: Installation and Configuration).   The supported version that is affected is 11.2.25.0.000. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Hyperion Infrastructure Technology executes to compromise Oracle Hyperion Infrastructure Technology.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Infrastructure Technology accessible data as well as  unauthorized access to critical data or complete access to all Oracle Hyperion Infrastructure Technology accessible data. CVSS 3.1 Base Score 6.3 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Hyperion Infrastructure Technology.

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

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

## Is CVE-2026-62558 being exploited?

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

## Other vulnerabilities in Oracle Hyperion Infrastructure Technology

- [CVE-2026-62457](https://insights.sbomify.com/CVE-2026-62457/): Auth bypass in Oracle Hyperion Infrastructure Technology (critical 9.8)
- [CVE-2026-62539](https://insights.sbomify.com/CVE-2026-62539/): Auth bypass in Oracle Hyperion Infrastructure Technology (critical 9.8)
- [CVE-2026-62541](https://insights.sbomify.com/CVE-2026-62541/): Auth bypass in Oracle Hyperion Infrastructure Technology (critical 9.8)
- [CVE-2026-62543](https://insights.sbomify.com/CVE-2026-62543/): Auth bypass in Oracle Hyperion Infrastructure Technology (critical 9.8)
- [CVE-2026-62544](https://insights.sbomify.com/CVE-2026-62544/): Auth bypass in Oracle Hyperion Infrastructure Technology (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62558 is a medium-severity missing authorization vulnerability in Oracle Hyperion Infrastructure Technology, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-62558 in the wild and no public exploit code.

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

## Sources

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

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