CVE-2026-47052·MySQL vulnerability
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.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 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).
- Severity
- medium
- Software
- MySQL
- Fixed in
- 8.0.46-0ubuntu0.22.04.4
- 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.44% — higher than 37% 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: 8.4.0
Until: 8.4.10
Fixed in: 8.0.46-0ubuntu0.22.04.4
How to fix this CVE
This InnoDB vulnerability allows high-privileged attackers to trigger a denial-of-service condition in MySQL Server, causing database hangs or crashes. Administrators should immediately upgrade affected MySQL versions (8.4.0–8.4.10, 9.7.0–9.7.1, and MySQL Cluster 8.0.0–8.0.47) to the patched release or newer. After upgrading, restart the MySQL service and verify connectivity to ensure normal operation is restored.
sudo dnf update mysql-server && sudo systemctl restart mysqldDefensia detects this vulnerability
How to check if you are affected
- Run `mysql --version` or `SELECT @@version;` from the MySQL client to confirm the installed version matches an affected release (8.4.0–8.4.10 or 9.7.0–9.7.1).
- Verify that the MySQL process is running with elevated privileges using `ps aux | grep mysqld` and note the user context.
- Search MySQL error logs (typically `/var/log/mysql/error.log` on Linux) for repeated crash dumps, assertion failures, or InnoDB recovery messages occurring after network access events.
- After applying the patch, confirm the new version with `SELECT @@version;` and monitor error logs for 24 hours to ensure no residual instability.
FAQ
What is CVE-2026-47052?
CVE-2026-47052 is an InnoDB denial-of-service vulnerability in Oracle MySQL that permits high-privileged network attackers to crash or hang the database server without requiring user interaction.
Is CVE-2026-47052 being actively exploited?
No, CVE-2026-47052 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits have been released. However, organizations should still prioritize patching due to the medium CVSS score and ease of exploitation by privileged insiders.
What versions of MySQL are affected by CVE-2026-47052?
MySQL Server versions 8.4.0–8.4.10 and 9.7.0–9.7.1 are affected, as well as MySQL Cluster 8.0.0–8.0.47, 8.4.0–8.4.10, and 9.7.0–9.7.1.
How do I check if my server is vulnerable to CVE-2026-47052?
Connect to your MySQL server with `mysql -u root -p` and run `SELECT @@version;`. If the version falls within 8.4.0–8.4.10 or 9.7.0–9.7.1, your server is vulnerable.
Does Defensia detect CVE-2026-47052?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MySQL is installed on a monitored server, CVE-2026-47052 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-47052. Free for 1 server.
Get started free