Live › vulnerability › CVE-2026-101624
Go to dashboardA flaw in the InnoDB storage engine of MySQL Server and MySQL Cluster can be triggered over the network by a high-privileged account to hang or repeatedly crash the server. The sources describe an availability impact only, with no data read or code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running MySQL Server or MySQL Cluster in the listed version ranges are exposed. The attacker needs a high-privileged database account and network access, so exposure is mostly a concern for shared or internet-reachable database hosts. Servers that already restrict database accounts tightly face lower risk.
No product ranges from the sources yet.
SELECT VERSION(); on the server and compare against the affected ranges: 8.0.0-8.0.49 (Cluster only), 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: InnoDB). Supported versions that are affected are MySQL Server: 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster: 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1. Easily exploitable vulnerability allows high privileged 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 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
This page as .md · .json · in your agent: get_signal("CVE-2026-101624")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.