⌁AI·CYBER·BRIEF▌
Vulnerabilities5 min read

Oracle's out-of-cycle patch fixes a 9.1 MySQL authentication flaw — details are thin, so patch first

CVE-2026-114952 lets an unauthenticated attacker read and change data on MySQL Server 8.4, 9.7 and 26.10, Oracle says. What's known, what isn't, and what to do today.

Oracle has released an out-of-cycle security update for MySQL fixing CVE-2026-114952, a flaw it rates 9.1 out of 10. According to Oracle, an attacker with network access and no credentials can exploit it easily to read, create, change or delete data on MySQL Server and MySQL Cluster. It was published on November 17, 2026, in Oracle's November Critical Security Patch Update. Oracle has disclosed very little else, and we found no report of exploitation so far. If you run MySQL on an affected version, plan to patch now and keep the database off the open network until you do.

What happened, in plain English

MySQL is one of the most widely used databases in the world. It sits behind websites, online shops, WordPress installs and business applications.

Oracle normally ships security fixes once a quarter. In 2026 it added a second channel, the Critical Security Patch Update (CSPU): smaller, targeted releases for problems that shouldn't wait for the next quarter. This MySQL fix arrived through that channel, a month after the October quarterly update. That alone signals Oracle thinks it is urgent.

Oracle's description is brief. It calls the flaw "easily exploitable" by an "unauthenticated attacker with network access via multiple protocols," and says a successful attack gives full read access and full ability to change data — but does not take the server down. CISA's enrichment of the CVE record classifies it as improper authentication (CWE-287). In everyday terms: under some conditions, the database's front door can be opened without the right key.

The odd detail is where Oracle files it: the "Client programs" component. In MySQL's terminology, that usually means the command-line tools that ship with the server — the mysql client, mysqldump, mysqladmin and so on — rather than the server's own login code. Oracle has not explained how a flaw in that component leads to an unauthenticated attacker compromising the server, and we have not been able to establish it independently. The score and the impact description are Oracle's; the mechanism is not public.

Are you affected? What to do now

Affected versions, per the CVE record and Oracle's advisory:

  • MySQL Server: 8.4.0 – 8.4.13, 9.7.0 – 9.7.4, and 26.10
  • MySQL Cluster: 8.0.0 – 8.0.50, 8.4.0 – 8.4.13, 9.7.0 – 9.7.4, and 26.10

The same advisory also lists MySQL Shell 26.10.0 and MySQL Workbench 26.10.0 among affected MySQL products, for other CVEs in the release.

Note what is not in the list: MySQL Server 8.0. Oracle lists 8.0 only for MySQL Cluster.

  • Find your MySQL instances and versions. SELECT VERSION(); or mysqld --version. Include the ones bundled with applications, control panels and containers.
  • Get the fix. Oracle's patch information is in My Oracle Support document CPU440, which requires a support login. For Community Edition, MySQL's release-notes pages listed a placeholder for 8.4.13.1 marked "not yet released" when we checked on November 18; watch the MySQL downloads page and your Linux distribution or cloud provider for patched packages. Managed services such as cloud MySQL offerings patch on their own schedule — check their changelogs.
  • Until you're patched, restrict who can reach the database. MySQL should almost never listen on the public internet. Bind it to a private interface (bind-address), allow port 3306 only from the application servers that need it, and put remote administration behind a VPN or SSH tunnel.
  • Remove accounts you don't need, especially anonymous users and accounts allowed from any host ('user'@'%'). This doesn't fix a pre-authentication flaw, but it narrows what any foothold reaches.
  • Check your logs and data for unexpected connections or changes, particularly on any instance that was reachable from the internet. With no indicators published, look for logins from unfamiliar addresses and unexplained schema or data changes.
  • Back up before you patch, and keep at least one copy that the database server itself can't write to.

The expert view

A 9.1 with this vector — network, low complexity, no privileges, no user interaction — is the profile of a bug that gets weaponised quickly once details emerge. The absence of an availability impact is informative: Oracle's assessment is that the attacker gets in and gets data, rather than crashing the server, which fits an authentication-logic flaw rather than memory corruption.

The "Client programs" classification deserves scepticism in both directions. It may mean the vulnerable code is shared between the client tools and the server's connection handling — MySQL's client library and protocol code are used on both sides — or that the attack involves a component most administrators don't think of as exposed. It may also mean the real-world exposure is narrower than the score suggests. Oracle's CVSS vectors describe the worst case, and its advisories are notoriously terse. Until there is a technical write-up or a diffable fixed release, defenders should treat it at face value: any MySQL server an attacker can reach over the network is at risk.

That makes network exposure the variable that matters most right now. Internet-wide scans routinely find large numbers of MySQL servers answering on port 3306 from the open internet. Those are the instances that will be hit first once exploitation details circulate — and the ones where restricting access today costs least. CISA's assessment that exploitation is "automatable" points the same way.

Two things we could not confirm. First, the exact fixed version numbers for Community Edition: Oracle's public advisory lists affected ranges and points to a support document, and the MySQL release notes had no published fix entry when we checked. Second, who found it and how: Oracle's credit section names Kentaro Takeda of YouMind for this CVE, with no further detail. (The same advisory credits Nicholas Carlini of Anthropic for an unrelated Java flaw, CVE-2026-114940.) We'll update this brief when Oracle or MySQL publish fixed release notes.

Official sources

Coverage: cve.now (aggregated record, no public exploit tracked).

Get the daily brief

AI + security signal by email: headlines, a two-line summary, a link. No noise, no spam.

How often