CVE-2026-21998·MySQL vulnerability
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.45, 8.4.0-8.4.8 and 9.0.0-9.6.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 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).
- Severity
- medium
- Software
- MySQL
- Fixed in
- 8.0.46-0ubuntu0.20.04.1+esm2
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 13% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 9.0.0
Until: 9.6.0
Fixed in: 8.0.46-0ubuntu0.20.04.1+esm2
How to fix this CVE
Update MySQL Server to version 8.0.46 or later to resolve a denial-of-service vulnerability in the query optimizer that allows high-privileged attackers to trigger server crashes. This patch addresses the issue where malicious SQL queries crafted by database administrators or compromised accounts can cause repeated service interruptions. Prioritize this update for production MySQL instances to restore availability protection.
sudo dnf update mysql-serverDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your MySQL version by running 'mysql --version' or connect to the server and run 'SELECT VERSION();' in the MySQL prompt
- Step 2: Verify if you are running version 8.0.0–8.0.45, 8.4.0–8.4.8, or 9.0.0–9.6.0, which are the confirmed vulnerable ranges
- Step 3: Review MySQL error logs for repeated 'Server shutdown' or 'crash recovery' messages that may indicate exploitation attempts: 'tail -f /var/log/mysql/error.log | grep -i crash'
- Step 4: After applying the patch, confirm the new version is active by running 'mysql --version' and restart the MySQL service: 'sudo systemctl restart mysql'
FAQ
What is CVE-2026-21998?
CVE-2026-21998 is a denial-of-service vulnerability in MySQL's query optimizer component that allows high-privileged attackers to craft specific SQL queries that cause the database server to hang or crash repeatedly, resulting in complete service unavailability.
Is CVE-2026-21998 being actively exploited?
No, this vulnerability is not currently listed on the CISA KEV catalog and no public exploits are known to exist. However, organizations should still patch promptly since high-privileged accounts (DBAs, compromised service accounts) can trigger the issue.
What versions of MySQL are affected by CVE-2026-21998?
MySQL Server versions 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, and 9.0.0 through 9.6.0 are vulnerable. Version 8.0.46 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-21998?
Run 'mysql --version' or log into MySQL and execute 'SELECT VERSION();' to determine your current version. If it falls within the affected ranges listed above, your instance is vulnerable.
Does Defensia detect CVE-2026-21998?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MySQL is installed on a monitored server, CVE-2026-21998 will appear in your dashboard with remediation steps.
Related MySQL CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-21998. Free for 1 server.
Get started free