# CVE-2026-60315: Information disclosure in MySQL Cluster

> Unauthenticated attackers can cause a denial of service and read a subset of data in MySQL Server and Cluster via the X Plugin.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-47wc-32xv-3x4v, MINI-4wpm-x9m5-5w39, MINI-565m-jwfv-6vjg, MINI-6xv4-m743-hv46, MINI-8qxr-7h8w-8rvj, MINI-992h-wqwm-42fw, MINI-gpc2-x52r-63xp, MINI-hh6p-5pxm-8vhf, MINI-j2r4-fq2h-rm4x, MINI-vgmv-hrhc-xqf8, UBUNTU-CVE-2026-60315

## What is CVE-2026-60315?

CVE-2026-60315 is a high-severity vulnerability in Oracle Mysql Cluster, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: X Plugin).  Supported versions that are affected are MySQL Server: 8.4.0-8.4.10, 9.7.0-9.7.1; MySQL Cluster: 8.0.0-8.0.47, 8.4.0-8.4.10 and  9.7.0-9.7.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster and  unauthorized read access to a subset of MySQL Server, MySQL Cluster accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Oracle Mysql Cluster, Oracle Mysql Server.

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

Apply the vendor's patch.

## Is CVE-2026-60315 being exploited?

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

## Other vulnerabilities in Oracle Mysql Cluster

- [CVE-2026-60163](https://insights.sbomify.com/CVE-2026-60163/): Privilege escalation in MySQL Cluster (high 8.4)
- [CVE-2026-60592](https://insights.sbomify.com/CVE-2026-60592/): Denial of service in MySQL Cluster (high 8.2)
- [CVE-2026-101772](https://insights.sbomify.com/CVE-2026-101772/): Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Client programs). (high 8.1)
- [CVE-2026-70724](https://insights.sbomify.com/CVE-2026-70724/): Auth bypass in MySQL Cluster (high 7.5)
- [CVE-2026-46863](https://insights.sbomify.com/CVE-2026-46863/): Denial of service in MySQL Cluster (high 7.5)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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