CVE-2026-60315
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVulnerability in MySQL X Plugin allows unauthenticated remote attackers with network access to cause a denial of service (complete DOS via hang or crash) and unauthorized read access to a subset of accessible data. The X Plugin exposes X Protocol and can be exploited without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.4.0, <= 8.4.10= 9.7.0= 9.7.1>= 8.0.0, <= 8.0.47>= 8.4.0, <= 8.4.10= 9.7.0= 9.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MySQL Server versionRun `mysql --version` or execute `SELECT VERSION();` in MySQL clientAffected if Version falls within 8.4.0 to 8.4.10, 9.7.0, 9.7.1 (Server) or 8.0.0 to 8.0.47, 8.4.0 to 8.4.10, 9.7.0, 9.7.1 (Cluster)
-
Verify if MySQL Cluster versionCheck product name via `mysqladmin version` or consult system documentation about the MySQL variant installedAffected if MySQL Cluster version is 8.0.0-8.0.47, 8.4.0-8.4.10, 9.7.0, or 9.7.1
-
Check if X Plugin is enabledExecute `SHOW PLUGINS LIKE 'mysqlx';` or inspect configuration files (my.cnf/my.ini) for `mysqlx` or `x-plugin` directives under `[mysqlx]` sectionAffected if The mysqlx plugin appears in plugin list or X Plugin configuration is present in config files
-
Verify X Protocol port statusCheck if port 33060 (default X Protocol) is listening using `netstat -an | grep 33060` or `ss -tlnp | grep 33060`Affected if Port 33060 is open and listening, indicating X Plugin is actively accepting connections
You are affected if your MySQL Server or Cluster version is within the listed vulnerable ranges AND the X Plugin is enabled (plugin loaded or X Protocol port is listening).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade MySQL Server or MySQL Cluster to a patched version beyond 8.4.10, 8.0.47, or 9.7.1. If patching is not immediately feasible, disable the X Plugin or restrict network access to it as a compensating control.
MySQL Server 8.4.11+, 9.7.2+; MySQL Cluster 8.0.48+, 8.4.11+, 9.7.2+
- 1. Identify the currently installed MySQL Server or MySQL Cluster version using: `mysql --version` or checking the MySQL service logs
- 2. For MySQL Server 8.4.x (versions 8.4.0-8.4.10), upgrade to MySQL Server 8.4.11 or later
- 3. For MySQL Server 9.7.x (versions 9.7.0-9.7.1), upgrade to MySQL Server 9.7.2 or later
- 4. For MySQL Cluster 8.0.x (versions 8.0.0-8.0.47), upgrade to MySQL Cluster 8.0.48 or later
- 5. For MySQL Cluster 8.4.x (versions 8.4.0-8.4.10), upgrade to MySQL Cluster 8.4.11 or later
- 6. For MySQL Cluster 9.7.x (versions 9.7.0-9.7.1), upgrade to MySQL Cluster 9.7.2 or later
- 7. After upgrade, verify the MySQL X Plugin version using: `mysql> SHOW VARIABLES LIKE 'mysqlx_version';`
- 8. Ensure the X Plugin is only bound to trusted interfaces if not needed, or consider disabling it if unused: `mysql> INSTALL PLUGIN mysqlx SONAME 'mysqlx.so';` (or UNINSTALL for disable)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data