CVE-2026-60188·MySQL vulnerability
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Replication). 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. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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.25% — higher than 17% 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 vulnerability in MySQL's replication component allows high-privileged attackers to trigger denial-of-service conditions through network protocols. Administrators should upgrade to the patched version 8.0.46-0ubuntu0.22.04.4 or later to eliminate the attack surface. Apply updates during a maintenance window to avoid disruption to active database services.
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();' in the MySQL client to check your installed version against the affected range 8.4.0–8.4.10
- Verify replication status by executing 'SHOW SLAVE STATUS\G;' or 'SHOW REPLICA STATUS\G;' to confirm if binary log replication is active on the server
- Search MySQL error logs (typically /var/log/mysql/error.log) for repeated crash messages or 'hang' messages coinciding with replication traffic, using: grep -i 'replication\|crash\|hang' /var/log/mysql/error.log
- After patching, confirm the new version with 'mysql --version' and restart the MySQL service to ensure the fix is loaded: sudo systemctl restart mysql && sudo systemctl status mysql
FAQ
What is CVE-2026-60188?
CVE-2026-60188 is a medium-severity denial-of-service flaw in MySQL Server's replication component that allows privileged network-based attackers to crash or hang the database engine, disrupting availability.
Is CVE-2026-60188 being actively exploited?
No, CVE-2026-60188 is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, organizations should still prioritize patching since high-privileged insider threats could exploit this.
What versions of MySQL are affected by CVE-2026-60188?
MySQL Server versions 8.4.0 through 8.4.10 and 9.7.0 through 9.7.1 are vulnerable. MySQL Cluster versions 8.0.0–8.0.47, 8.4.0–8.4.10, and 9.7.0–9.7.1 are also affected.
How do I check if my server is vulnerable to CVE-2026-60188?
Connect to MySQL and run 'SELECT VERSION();' to display your version, then verify it falls within the affected ranges. Cross-check against the official Oracle security advisory at https://www.oracle.com/security-alerts/cpujul2026.html.
Does Defensia detect CVE-2026-60188?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MySQL is installed on a monitored server, CVE-2026-60188 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-60188. Free for 1 server.
Get started free