Go straight to an AI summary of this blog post instead

  • Summarize this post with Perplexity
  • Summarize this post with Gemini

Status Update for November 18, 2026

Oracle published CVE-2026-114952 on November 17 in its November Critical Security Patch Update. For now the fix is available only to Oracle support customers through My Oracle Support, and it hasn’t appeared in the public MySQL source.

TuxCare is tracking the fix for the MySQL 8.0 and Percona Server 8.0 builds covered by Endless Lifecycle Support. MySQL 5.1 and 5.7 builds are awaiting assessment. This status note will be updated as things change.

Get Endless Lifecycle Support for MySQL →

Key Takeaways

  • CVE-2026-114952 is a CVSS 9.1 MySQL flaw Oracle says needs no authentication or user interaction.
  • Oracle’s list skips MySQL Server 8.0, which moved to Sustaining Support in April 2026, so it wasn’t tested.
  • Oracle points to MySQL’s client programs, so app servers, backup hosts and jump hosts need checking too.
  • No exploitation has been publicly reported, but CISA’s SSVC data marks it automatable with total technical impact.

The Short Version

Jump to the Long Version ↓

What happened. On November 17, Oracle published CVE-2026-114952 as part of its November 2026 Critical Security Patch Update. It scores 9.1 and sits in the “Client programs” component of MySQL Server and MySQL Cluster. Jump to this section →

Who’s affected. Oracle names MySQL Server 8.4.0 through 8.4.13, 9.7.0 through 9.7.4 and 26.10, plus MySQL Cluster 8.0.0 through 8.0.50 and the same newer lines. MySQL Server 8.0, 5.7 and older aren’t on the list because Oracle doesn’t test releases outside Premier or Extended Support, not because anyone cleared them. Jump to this section →

How bad it is. It’s reachable over the network with no credentials and no user interaction, and the impact on data confidentiality and integrity is high. No exploitation has been publicly reported so far. Jump to this section →

Where things stand. Oracle’s fix is available only through My Oracle Support so far, and no fixed version has shown up in the public MySQL source tree. Ubuntu is still evaluating its MySQL 8.0 packages and has marked 5.7 as ignored. TuxCare is tracking the fix for its MySQL 8.0 and Percona Server 8.0 builds, and its 5.1 and 5.7 builds are awaiting assessment. Jump to this section →

What to do today. Find every host with MySQL binaries on it, not just the database servers. Lock down which hosts can reach MySQL ports, and work out where each of your versions will get its fix. Jump to this section →

The Long Version

Oracle’s November Critical Security Patch Update landed on November 17 with 655 new security patches across its product families, and one MySQL entry stood out. CVE-2026-114952 carries a CVSS 3.1 score of 9.1, can be triggered over the network without credentials and lives in the client programs, the part of MySQL that tends to get missed when patching is all about the database servers.

The risk matrix is thin on detail. Oracle doesn’t name the affected binary, doesn’t describe the bug class and hasn’t published a workaround. What it does publish is a version list, and that list has a gap that matters to a lot of production databases.

MySQL Server 8.0 isn’t on it. Oracle left it off because 8.0 dropped out of Extended Support in April 2026, which means Oracle never tested it. Teams still running 8.0 are left with a critical advisory and no answer about their own servers. The rest of this post separates what Oracle has confirmed from what’s still inference, then walks through how to check your hosts.

What Oracle Actually Disclosed

The fix shipped in the November 2026 CSPU, the monthly security release Oracle now runs between its quarterly Critical Patch Updates. MySQL picked up 10 new security patches in this round. A MySQL Shell issue scored higher at 9.8, but Oracle files that one under the Python runtime bundled with Shell. CVE-2026-114952 is the top-scoring issue in MySQL Server and MySQL Cluster.

Here’s what the risk matrix says. The component is “Client programs,” the protocol is the MySQL Protocol and the answer to “remote exploit without authentication” is yes. The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Oracle credits the find to Kentaro Takeda of YouMind. The CVE ID was reserved on October 22, almost four weeks before the advisory went out, and nothing public suggests it was exploited before then.

Oracle’s description says a successful attack can give an attacker unauthorized ability to create, delete or modify critical data, plus unauthorized access to it. Availability impact is rated None. So the worry here is data theft and data tampering, not a crashed server.

One practical wrinkle for anyone on community builds. As of November 18, the fix is only available to Oracle support customers through My Oracle Support. The newest tags in Oracle’s public MySQL source repository are still 8.4.13, 9.7.4 and 26.10.0, the same versions listed as affected.

Why Client Programs Change the Hunt

In MySQL’s packaging, “client programs” covers the command-line tools that ship alongside the server, such as mysql, mysqldump, mysqladmin, mysqlbinlog, mysqlcheck and mysqlimport. Oracle files this bug under that component but hasn’t said which tool, or which shared code, is affected. For now, the point is that these tools also get installed on lots of systems that never run mysqld.

App servers keep them around for migrations and one-off fixes. Backup hosts often run mysqldump on a schedule. Jump hosts and admin workstations collect whatever client version someone installed years ago. Container images bake them in and keep them until somebody rebuilds the image.

Oracle also hasn’t described the attack path. It could be a client mishandling data from a malicious server, some other client-side weakness or something else entirely. The first kind has precedent. The rogue server trick that abuses LOAD DATA LOCAL INFILE to pull files off a connecting client has been public for years. Nothing ties that technique to this CVE, though, so treat it as an example of the risk, not an explanation. Until details come out, assume any host with a potentially affected MySQL client installed is in scope, whether or not it runs a database.

This component has come up before, too. Oracle’s October 20 Critical Patch Update fixed three other unauthenticated network flaws filed under “Client programs,” CVE-2026-101770, CVE-2026-101771 and CVE-2026-101772, each rated 8.1. That’s four in two consecutive updates.

Who Is Exposed?

Oracle’s list for MySQL Server covers 8.4.0 through 8.4.13, 9.7.0 through 9.7.4 and 26.10. For MySQL Cluster, it’s 8.0.0 through 8.0.50, 8.4.0 through 8.4.13, 9.7.0 through 9.7.4 and 26.10. The top of each range lines up with the newest public builds from before the advisory, so being fully up to date before November 17 didn’t help.

Forks need their own answer. Percona Server for MySQL is built on upstream MySQL, so it may well be affected until Percona publishes its own assessment. MariaDB forked from MySQL in 2009, and Ubuntu currently lists its MariaDB packages as “Needs evaluation.” Don’t assume either fork is affected or safe until its maintainers weigh in.

The MySQL 8.0 Problem

Oracle’s advisory is upfront about why 8.0 is missing. Releases outside Premier Support or Extended Support aren’t tested for the vulnerabilities in the advisory, and Oracle says it’s likely that earlier versions of affected releases are also affected. MySQL 8.0’s Extended Support ended in April 2026, so MySQL Server 8.0 wasn’t evaluated.

Now look at the Cluster line. MySQL Cluster 8.0.0 through 8.0.50 is on the affected list for the same component. That doesn’t prove MySQL Server 8.0 carries the same flaw, and Oracle hasn’t said it does, but it’s the best public evidence available. October’s three client programs flaws followed the same pattern. Cluster 8.0 was listed and Server 8.0 wasn’t, and Ubuntu later shipped fixes for all three in its MySQL 8.0 packages for 22.04 and 24.04. Taken together, it’s a strong signal that the 8.0 series may contain the vulnerable code.

So teams running self-managed MySQL Server 8.0 should treat it as potentially affected, and they shouldn’t expect a fix from Oracle. Oracle’s managed HeatWave service is the exception. It keeps applying critical security patches until April 2027 to instances running MySQL 8.0.46 or later on Oracle Linux 8.

Versions 5.7 and older are a harder call. Oracle stopped evaluating 5.7 when it reached end of life in October 2023, and it hasn’t published anything showing whether the vulnerable code goes back that far. It depends on whether the bug sits in long-standing client code or in something added during the 8.0 series, and Oracle hasn’t said. Ubuntu has marked its MySQL 5.7 packages on 16.04 and 18.04 as “ignored” for this CVE, but that’s because upstream support has ended, not because anyone found them safe. Until that question is answered, treat 5.7 and older as possibly affected and keep their network exposure to a minimum.

How Serious Is It Really?

By the numbers, this one is bad. The flaw is reachable over the network with low attack complexity, and it needs neither privileges nor user interaction. Confidentiality and integrity impact are both rated High. It lands at 9.1 rather than 9.8 because availability impact is rated None.

CISA’s enrichment of the CVE record adds context. Its Stakeholder-Specific Vulnerability Categorization (SSVC) entry lists Exploitation as “none,” Automatable as “yes” and Technical Impact as “total.” CISA also assigned CWE-287, Improper Authentication. As of November 18, the CVE isn’t in CISA’s Known Exploited Vulnerabilities catalog. Ubuntu currently rates it “Medium” priority, so distro priorities and the CVSS score don’t line up here.

Treat this as urgent on any system where MySQL connections cross a network you don’t fully control, and on any host whose client tools connect to servers outside your environment. On tightly segmented internal networks the risk is lower – but it isn’t zero. And if a working proof of concept goes public, the attack gets much easier to reproduce.

Vendor and Distro Status

Status as of November 18, 2026.

Vendor Package or Version Status
Oracle MySQL Server 8.4, 9.7, 26.10 Fixed in the November 2026 CSPU, available through My Oracle Support
Oracle MySQL Server 8.0 and older Not assessed, outside Premier and Extended Support
Ubuntu mysql-8.0 on 20.04, 22.04 and 24.04 Needs evaluation
Ubuntu mysql-8.4 on 26.04 and mysql-9.7 on 26.10 Needs evaluation
Ubuntu mysql-5.7 on 16.04 and 18.04 Ignored, no upstream support
Debian MySQL and MariaDB packages No package status yet
Red Hat MySQL module streams No public CVE page or security data yet
NVD CVE record Received

What to Do Before the Patch Lands

Start with a decision. If you run MySQL 8.4, 9.7 or 26.10 with an Oracle support contract, get the fixed builds from My Oracle Support and schedule the update now. If you run community builds, watch the MySQL release notes and download pages until fixed community versions appear. Oracle’s next quarterly Critical Patch Update is due January 19, 2027, if nothing turns up sooner. If you run distro packages, follow your distro’s tracker. If you’re on self-managed 8.0, 5.7 or anything older, don’t expect a fix from Oracle. The real choices are an upgrade project, security support from a vendor that backports fixes to your version or formally accepting the risk.

While that plays out, cut down the exposure. Restrict access to port 3306, and 33060 if the X Protocol is enabled, to the specific hosts that need it. Production MySQL ports shouldn’t be reachable from the public internet anyway.

Make clients verify the servers they connect to. On clients that support it, which means 5.7.11 and later, --ssl-mode=VERIFY_IDENTITY with a trusted CA certificate checks the server’s certificate and hostname, so a script can’t be quietly pointed at a server it doesn’t trust. Older clients need their own version-specific TLS settings. Where nobody needs local file loading, turn it off with --local-infile=0.

Be careful putting these in my.cnf. Every client tool reads the [client] group, and most of them stop on an option they don’t recognize. That means local-infile=0 belongs under [mysql], because mysqldump and friends don’t know it and your backups will fail. ssl-mode=VERIFY_IDENTITY can go under [client] only if every client reading that file is 5.7.11 or newer. These are general hardening steps, not confirmed mitigations for this CVE, since Oracle hasn’t described the mechanism.

Then clean house. Pull client packages off hosts that don’t need them, and rebuild container images that ship MySQL clients so the next patch actually reaches them.

A Quick Check for Your Servers

Start with installed MySQL and Percona packages. These commands won’t catch every installation, so follow them with the binary and container checks below. On RHEL-family systems, run this.

rpm -qa | grep -Ei 'mysql|percona'

On Debian and Ubuntu, run this instead.

dpkg -l | grep -Ei 'mysql|percona'

Then look for client binaries on your PATH. This loop works in any POSIX shell.

for bin in mysql mysqldump mysqladmin mysqlbinlog mysqlcheck mysqlimport; do command -v "$bin"; done

The loop only searches PATH, so tarball and vendor-bundled installs under places like /opt or /usr/local/mysql/bin need a manual look.

Check the local client versions directly.

mysql --version
mysqldump --version

Then ask each server for its own version. This connects to whatever server your client is configured for, which may be remote, so supply credentials and a host as needed.

mysql -u root -p -e "SELECT VERSION();"

For containers, start with images named after MySQL or Percona. Application images can carry client tools under any name, so check their package lists or SBOMs too.

docker images | grep -Ei 'mysql|percona'

Reading the results is straightforward. Oracle confirms 8.4.0 through 8.4.13, 9.7.0 through 9.7.4 and 26.10 as affected. Treat MySQL Server 8.0 as potentially affected based on the Cluster listing and the October precedent, and treat 5.7 and older as unresolved until they’ve been assessed. On ELS hosts, TuxCare’s documented repository check for MySQL is yum info els-mysql-release. For Percona Server, it’s yum info els-percona-release on EL or apt-cache show els-percona-release on Ubuntu.

Where Endless Lifecycle Support Stands

TuxCare’s public CVE tracker already has an entry for CVE-2026-114952. No ELS fix has been released yet for MySQL 8.0 or Percona Server 8.0, because Oracle’s fix hasn’t reached the public MySQL source. MySQL 5.1 and 5.7 are awaiting assessment. This section will be updated as that changes.

TuxCare Offering Platforms Version Status (November 18, 2026)
ELS for MySQL EL 7 and EL 8 MySQL 8.0 Not released, upstream fix not public yet
ELS for Percona Server EL 7, EL 8, Ubuntu 22.04 and Ubuntu 24.04 Percona Server 8.0 Not released, upstream fix not public yet
ELS for OS CentOS 6 and Oracle Linux 6 MySQL 5.1 Awaiting assessment
ELS for OS Ubuntu 16.04 and Ubuntu 18.04 MySQL 5.7 Awaiting assessment

When ELS fixes ship for 8.0, they arrive as package updates inside the existing 8.0 line, through yum on EL systems and apt for Percona Server on Ubuntu. Covered security fixes don’t require a jump to 8.4 or a dump and restore. As with any database update, test replication and application behavior before rolling it out.

Get Endless Lifecycle Support for MySQL →

The Bottom Line

Thin public detail doesn’t make a 9.1 any less serious. Teams on 8.4, 9.7 and 26.10 have a clear path through Oracle’s update, even if community users have to wait for a public release. The harder spot belongs to everyone on self-managed MySQL 8.0 and older. Oracle hasn’t said whether their versions contain the vulnerable code, and those releases don’t get upstream fixes anymore.

Treat the missing 8.0 entry as possible exposure until someone shows otherwise. Inventory the client tools along with the servers, tighten network paths and put a remediation plan in place for every affected version you run. Teams that need MySQL 8.0 covered while they upgrade on their own schedule are exactly who TuxCare’s extended support is built for.

Get Endless Lifecycle Support for MySQL →

Timeline

Date Event
October 20, 2026 Oracle’s October Critical Patch Update fixes three earlier client programs flaws, CVE-2026-101770, CVE-2026-101771 and CVE-2026-101772
October 22, 2026 Oracle reserves the CVE ID
November 17, 2026 Oracle publishes the November 2026 CSPU and the CVE record, with a CVSS 3.1 score of 9.1
November 17, 2026 CISA adds SSVC data and CWE-287 to the CVE record
November 18, 2026 Ubuntu publishes its tracker entry and begins package evaluation
November 18, 2026 Oracle’s fix is still absent from the public MySQL source, and TuxCare begins tracking it for ELS builds of MySQL 8.0 and Percona Server 8.0
December 15, 2026 Next scheduled Oracle CSPU
January 19, 2027 Next scheduled Oracle quarterly Critical Patch Update

Sources

Oracle Critical Security Patch Update Advisory, November 2026

Oracle CSPU November 2026, text form of the risk matrices

CVE record for CVE-2026-114952

NVD entry for CVE-2026-114952

Ubuntu CVE tracker entry

Debian security tracker entry

MySQL Community Edition Security Advisory, October 2026

Ubuntu CVE tracker entry for CVE-2026-101770

Ubuntu CVE tracker entry for CVE-2026-101771

Ubuntu CVE tracker entry for CVE-2026-101772

Oracle HeatWave release note on MySQL 8.0 support until April 2027

MySQL Server source repository on GitHub

TuxCare CVE tracker entry

TuxCare documentation for ELS for MySQL

TuxCare documentation for ELS for Percona Server

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.

Table of Contents
Get the open-source security answers you need

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.