Skip to content

Oracle patches a critical MySQL bug, but not for version 8.0

November's Critical Patch Update fixes CVE-2026-114952, a 9.1 pre-auth flaw in MySQL Server and Cluster client programs, but 8.0 was left off the affected list entirely.

Source: Oracle

Oracle’s November Critical Patch Update, released on 17 November, fixes CVE-2026-114952, a critical bug in MySQL Server and MySQL Cluster’s client programs. It carries a CVSS v3.1 score of 9.1 and needs no authentication or user interaction, just network access, to exploit.

The fix covers MySQL Server 8.4.0 to 8.4.13, 9.7.0 to 9.7.4 and 26.10, plus the matching Cluster releases. MySQL 8.0 is not on that list. It left Oracle’s Extended Support in April, so Oracle did not test it against this bug and is not shipping a fix for it. The patch itself is only available to Oracle support customers through My Oracle Support; it has not reached MySQL’s public source yet.

Why it matters: if you are still running self-managed MySQL 8.0, which remains common, you have no official patch to apply and no word from Oracle on whether you are exposed. Moving to 8.4 or later is now the only route to a fix, not just the recommended one.

The caveat: Oracle’s advisory does not list this bug as currently exploited, but a pre-auth, no-interaction critical in a database this widely run tends not to stay quiet for long once the patch diff is public.

Share

Related reading

More from The Wire

All briefs

A Linux KVM bug let one VM read 127GB of host memory

A bug bounty researcher used a four-year-old stale pointer in nested virtualization to read host kernel memory from inside an ordinary cloud VM. DigitalOcean disclosed and patched it as CVE-2026-99312.

via DigitalOcean