Quick answers
- Is CVE-2026-60315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60315 being exploited in the wild.
- How severe is CVE-2026-60315?
- High severity, with a CVSS score of 8.2, published 21 July 2026.
- Which products and versions are affected?
- Oracle MySQL Server 8.4.0-8.4.10, 9.7.0-9.7.1; Oracle Mysql Cluster 8.0.0-8.0.47, 8.4.0-8.4.10, 9.7.0-9.7.1.
- Is there a fix for CVE-2026-60315?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-60315 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-60315?
- Check whether you run Oracle MySQL Server or Oracle Mysql Cluster at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the X Plugin component of Oracle MySQL Server and MySQL Cluster. It is classified as an easily exploitable flaw that allows an unauthenticated attacker with network access via multiple protocols to compromise the server. Successful exploitation can lead to a complete denial-of-service (DoS) by causing the server to hang or crash repeatedly. Additionally, the attacker can gain unauthorized read access to a subset of the data stored in the database. The vulnerability affects MySQL Server versions 8.4.0 through 8.4.10 and 9.7.0 through 9.7.1, as well as MySQL Cluster versions 8.0.0 through 8.0.47, 8.4.0 through 8.4.10, and 9.7.0 through 9.7.1.
Affected products
- Oracle MySQL Server 8.4.0-8.4.10, 9.7.0-9.7.1
- Oracle MySQL Cluster 8.0.0-8.0.47, 8.4.0-8.4.10, 9.7.0-9.7.1
Timeline
- 2026-07-21: advisory: Oracle published the vulnerability details in the July 2026 CPU.
- 2026-07-21: disclosed