# CVE-2026-60526: Other in Oracle Java SE

> A vulnerability in Oracle Java SE allows a low-privileged attacker with local access to compromise the runtime, potentially leading to full takeover.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 1 Aug 2026
- **Also known as:** BIT-java-2026-60526, BIT-java-min-2026-60526, BIT-jre-2026-60526, GHSA-8658-gj58-hrr8, MINI-mp7f-whhj-ghm3

## What is CVE-2026-60526?

CVE-2026-60526 is a medium-severity vulnerability in Oracle Jdk, published on 21 Jul 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 Oracle Java SE (component: Installation).  Supported versions that are affected are Oracle Java SE: 8u491 and  8u491-perf. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Java SE executes to compromise Oracle Java SE.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Java SE. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H).

Weakness: CWE-20 (Improper Input Validation)

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

3 open source packages ship an affected version, including java, java-min and jre. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java` | Bitnami | All versions | 1.8.0, 8.0.501 |
| `java-min` | Bitnami | All versions | 1.8.0, 8.0.501 |
| `jre` | Bitnami | All versions | 1.8.0, 8.0.501 |

Products: Oracle Jdk, Oracle Jre.

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

Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.501.

## Is CVE-2026-60526 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60526 is a medium-severity vulnerability in Oracle Jdk, published on 21 Jul 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-60526 in the wild and no public exploit code.

Affected packages and fixed versions:
- java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.501
- java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.501
- jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.501

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-60526/ (Markdown: https://insights.sbomify.com/CVE-2026-60526/index.md)
```

## Sources

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

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