dbcve.org
Mysql ClusterDatabase / datastore · Oracle

CVE-2026-46863

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 9.7.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Connection Handling). Supported versions that are affected are MySQL Server: 8.4.0-8.4.9, 9.0.0-9.7.0; MySQL Cluster: 8.0.11-8.0.46, 8.4.0-8.4.9 and 9.0.0-9.7.0. 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. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 confidence

This is a denial-of-service vulnerability in MySQL Server and MySQL Cluster's connection handling component. An unauthenticated attacker with network access can send specially crafted connection requests that cause the MySQL server to hang or crash repeatedly, resulting in complete service unavailability.

MitigationUpgrade MySQL Server and MySQL Cluster to versions beyond the affected ranges (8.4.10+, 9.0.8+, or later patched versions). If immediate patching is not possible, restrict network access to MySQL ports (3306/TCP for MySQL, 1186 for Cluster) to trusted sources only.

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
Mysql ClusterDatabase / datastore
Affected:>= 8.0.11, <= 8.0.46>= 8.4.0, <= 8.4.9>= 9.0.0, <= 9.7.0
Mysql ServerDatabase / datastore
Affected:>= 8.4.0, <= 8.4.9>= 9.0.0, <= 9.7.0

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MySQL installation and version
    Run 'mysql --version' or 'mysqld --version' from command line, or query 'SELECT VERSION();' if you have a database connection
    Affected if Version falls within 8.0.11-8.0.46, 8.4.0-8.4.9, or 9.0.0-9.7.0 for Cluster; or 8.4.0-8.4.9 or 9.0.0-9.7.0 for Server
  2. Confirm product type (Server vs Cluster)
    Check if this is MySQL Cluster (NDB) or MySQL Server by reviewing installation packages, service name, or querying 'SHOW VARIABLES LIKE "innodb_version";' to verify Server, or checking for ndbinfo database presence for Cluster
    Affected if Running MySQL Cluster 8.0.11-8.0.46, 8.4.0-8.4.9, or 9.0.0-9.7.0; OR MySQL Server 8.4.0-8.4.9 or 9.0.0-9.7.0
  3. Verify network exposure of MySQL port
    Run 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306' to check if MySQL port is listening; verify firewall rules allow external connections (for Cluster also check port 1186)
    Affected if Port 3306/TCP (or 1186 for Cluster) is bound to 0.0.0.0 or externally accessible IP address, enabling unauthenticated network attackers to reach the service
  4. Confirm MySQL service is running
    Check service status via 'systemctl status mysql' or 'systemctl status mysqld' (or 'service mysql status'), or verify process is active via 'ps aux | grep mysql'
    Affected if MySQL service is currently running and accepting connections

Your environment is affected if you are running a vulnerable MySQL Server (8.4.x or 9.x) or MySQL Cluster (8.0.x, 8.4.x, or 9.x) version within the affected ranges and the database port is network-accessible to untrusted attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 9.7.0
Interim mitigation

Upgrade MySQL Server and MySQL Cluster to versions beyond the affected ranges (8.4.10+, 9.0.8+, or later patched versions). If immediate patching is not possible, restrict network access to MySQL ports (3306/TCP for MySQL, 1186 for Cluster) to trusted sources only.

Recommended fix High confidence

MySQL Server/Cluster 8.4.10+, 8.0.47+, or 9.7.1+ depending on your major version branch

  1. 1. Identify the exact MySQL Server or MySQL Cluster version currently installed using: `mysql --version` or `SELECT VERSION();`
  2. 2. For MySQL Server 8.4.x: upgrade to MySQL Server 8.4.10 or later
  3. 3. For MySQL Server 9.0.x-9.7.x: upgrade to MySQL Server 9.7.1 or later
  4. 4. For MySQL Cluster 8.0.x: upgrade to MySQL Cluster 8.0.47 or later
  5. 5. For MySQL Cluster 8.4.x: upgrade to MySQL Cluster 8.4.10 or later
  6. 6. For MySQL Cluster 9.0.x-9.7.x: upgrade to MySQL Cluster 9.7.1 or later
  7. 7. Download the appropriate MySQL installation packages from https://dev.mysql.com/downloads/
  8. 8. Back up all databases before performing the upgrade
Caveat Review MySQL upgrade notes for potential incompatibilities; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mysql Cluster Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46863 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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