MySQL is widely used enterprise software; vulnerability allows full server/cluster takeover, posing widespread operational and data risk.
CVE-2026-60163
Local flaw in MySQL Group Replication plugin enables server/cluster takeover.
Is CVE-2026-60163 being exploited?
Not confirmed. CVE-2026-60163 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-60163?
CVE-2026-60163 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-60163?
Yes. A fix has been recorded for CVE-2026-60163. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-60163 affect?
CVE-2026-60163 affects MySQL Server 8.4.0-8.4.10, MySQL Server 9.7.0-9.7.1, MySQL Cluster 8.0.0-8.0.47, MySQL Cluster 8.4.0-8.4.10, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-60163?
Isolate DB hosts, restrict access, apply vendor patch ASAP.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker with access to host can fully compromise MySQL Server/Cluster: execute code, steal/modify/delete data (C/I/A: High).
Immediate action required
- affected8.0.0-8.0.47
- affected8.4.0-8.4.10
- affected9.7.0-9.7.1
- affected8.4.0-8.4.10
- affected9.7.0-9.7.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.