Oracle MySQL November 2026 CSPU: One Critical Client-Side Flaw and Five High-Impact Bugs Analyzed
Oracle MySQL November 2026 CSPU: Analysis of CVE-2026-114949, CVE-2026-114950, CVE-2026-114951, CVE-2026-114952, CVE-2026-114953 and CVE-2026-127428
Summary: On November 17, 2026, Oracle published its November Critical Security Patch Update (CSPU), which contains 10 new MySQL security patches. Six of the CVEs from that update are the subject of this post: CVE-2026-114949, CVE-2026-114950, CVE-2026-114951, CVE-2026-114952, CVE-2026-114953 and CVE-2026-127428. All six affect MySQL Server and MySQL Cluster, and they sit in five different components: client programs, replication, the optimizer, logging and GIS.
Severity reality check: these are widely described as "critical", but only one of them is. The word comes from the name of the update program ("Critical Security Patch Update"), not from the CVSS scores. By Oracle's own CVSS 3.1 scoring, CVE-2026-114952 is Critical (9.1) and needs no credentials, three CVEs are High (7.2) but need an administrative account, CVE-2026-127428 is High (7.1) for a low-privileged account, and CVE-2026-114953 is Medium (6.5). The highest-scored MySQL item in the same update, CVE-2026-115557 at 9.8, is a MySQL Shell issue that is not in this list (see the section on the rest of the update).
What is and is not known: Oracle does not publish root causes, weakness types or exploit conditions. For CVE-2026-114952, the CISA ADP enrichment on the CVE record lists CWE-287 (Improper Authentication); that classification is CISA's, not Oracle's. As of November 19 we identified no public proof of concept and no reported exploitation, and none of the six is in the CISA Known Exploited Vulnerabilities catalog. Oracle's affected ranges include the newest community releases we could find (8.4.13, 9.7.4 and 26.10), so fixes arrive through Oracle's patch channel and later releases, not through a simple "upgrade to latest". Priority one is the unauthenticated CVE-2026-114952. Oracle lists its component only as "Client programs" and does not name the affected executables, so installations of MySQL client tools need assessment rather than being assumed vulnerable.
Overview
114952: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N114949, 114950, 114951: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H127428: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H114953: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HWhy "Critical" Is Misleading Here
Oracle ships security fixes in two forms. The quarterly Critical Patch Update (CPU) is large and cumulative: the October 2026 CPU carried 98 new MySQL patches, 29 of them remotely exploitable without authentication. In between, the Critical Security Patch Update (CSPU) is a smaller, targeted release. Oracle describes it as high-priority fixes in a "smaller, more focused format". "Critical" is part of the program name. It says nothing about the CVSS score of any individual CVE in the release.
That naming is the likely source of the "critical MySQL CVEs" headlines. The scores tell a more nuanced story, and the nuance changes patch order.
The attacker prerequisite matters more than the score
Four of the six scores are driven by one number: privileges required. A 7.2 that needs an administrative account describes a very different attacker from a 9.1 that needs nothing. The ladder below sorts the six by what an attacker must already hold.
What Oracle Published, and What It Did Not
This is a research post on bugs whose internals are not public. Oracle's disclosure policy is to publish a risk matrix and a short description, not technical detail. To keep this analysis honest, the table separates published fact from everything else. Anything beyond the left column is labeled as inference in the rest of the post.
| Published by Oracle | Not publicly disclosed (as of November 19, 2026) |
|---|---|
| Component per CVE (client programs, replication, optimizer, logging, GIS) | Which function, binary or code path is affected |
| CVSS 3.1 vector and base score | Root cause, and an Oracle-stated weakness type (the CISA ADP enrichment lists CWE-287 for CVE-2026-114952) |
| Privilege required and whether exploitation is remote without authentication | The trigger: a crafted statement, a crafted packet, a crafted server response, or a configuration |
| Affected version ranges | Fixed community version numbers (the affected ranges include the latest community releases found) |
| Impact class in Oracle's standard wording (takeover, data access, denial of service) | Proof of concept, exploit code or in-the-wild reports |
| Reporter credits for three of the six | A workaround specific to any of these CVEs |
The Six CVEs, One by One
CVE-2026-114952: Client Programs (9.1 Critical)
| Field | Detail |
|---|---|
| Component / protocol | Client programs · MySQL Protocol (Oracle's text: "multiple protocols") |
| Remote without authentication | Yes · attack complexity low · no user interaction |
| Impact | Confidentiality High, integrity High, availability None: unauthorized creation, deletion or modification of critical data, plus unauthorized access to critical or all accessible data |
| Credit | Kentaro Takeda |
| CVE ID reserved | October 22, 2026 |
| Weakness type | Not stated by Oracle. The CISA ADP container on the CVE record lists CWE-287 (Improper Authentication); this is CISA's classification, not Oracle's. |
What "Client programs" covers. MySQL's client programs are the command-line tools that ship with the product and talk to a server over the MySQL protocol, for example mysql, mysqldump, mysqlbinlog, mysqladmin, mysqlcheck, mysqlimport, mysqlshow and mysqlslap (the mysqlpump utility was removed in MySQL 8.4.0 and is not part of the 8.4, 9.7 or 26.10 releases). Oracle lists the component only as "Client programs". It does not say which executable or code path is affected. We therefore do not treat every client utility, or every client-only installation, as confirmed vulnerable.
What does follow from the component label is narrower: the flaw is attributed to client-side code, and a machine does not need to run a database server to carry that code. Application servers, bastion hosts, backup and batch nodes, CI runners and container images that include MySQL client programs should be assessed against Oracle's guidance and your vendor's fix information, instead of being skipped in database patch plans.
Possible exploitation models (hypothetical, not confirmed). Oracle has not disclosed the attack path. A client-side flaw scored as needing "no credentials" and "network access" could, in principle, mean that the attacker does not need to log in to anything, for example by being on the other end of a connection the client opens. That is speculation. Oracle's listing of the protocol as "MySQL Protocol" with the remote-unauthenticated flag does not establish it, and none of the recommendations or mappings in this post depend on it.
Why it is the first item to look at. It is the only one of the six scored with no credential requirement. Oracle's vector is network access, low complexity and no user interaction, with High confidentiality and integrity impact and no availability impact. CISA's SSVC enrichment on the CVE record, assessed on November 17, 2026, rates it exploitation: none, automatable: yes, technical impact: total. There is no known exploitation yet.
Context: the same component appeared in October
CVE-2026-114952 is not the first "Client programs" entry this autumn. Oracle's October 20, 2026 Critical Patch Update, as reproduced on MySQL's Community Edition security advisory page, listed several. The October entries are a useful comparison for how this component has been scored, and for how it has been judged downstream.
| CVE (October CPU) | Component | CVSS | Vector summary |
|---|---|---|---|
| CVE-2026-101770, CVE-2026-101771, CVE-2026-101772 | Client programs | 8.1 each | Network, attack complexity High, no privileges, no user interaction, C:H, I:H, A:H |
| CVE-2026-101679 | Client programs | 7.5 | Network, attack complexity Low, no privileges, availability impact only (A:H) |
| CVE-2026-101797 | Client: mysqldump | 7.5 | Network, attack complexity High, user interaction required, C:H, I:H, A:H |
| CVE-2026-114952 (November) | Client programs | 9.1 | Network, attack complexity Low, no privileges, no user interaction, C:H, I:H, A:N |
Three things stand out. First, the October entries covered MySQL Server 8.4.0 to 8.4.12, 9.7.0 to 9.7.3 and 26.7.0 to 26.7.1, while the November ranges run up to 8.4.13, 9.7.4 and 26.10, the releases that followed. That is consistent with November being a separate issue, although Oracle does not say so. Second, Oracle used a specific label, "Client: mysqldump", for one October entry, so "Client programs" is the general label and Oracle has not said which tools it covers in either month. Third, November is the first of these to combine low attack complexity with no user interaction, which is why it scores higher.
How a distribution vendor read the October siblings. Red Hat rated CVE-2026-101770, CVE-2026-101771 and CVE-2026-101772 as Important rather than Critical. Its reasoning was the high attack complexity and the point that, in typical deployments, client tools run in controlled administrative sessions or backend scripts, so practical exposure is limited to environments where client tooling interacts directly with untrusted network traffic. This is one vendor's assessment of related CVEs, not a statement about CVE-2026-114952. It does reinforce the approach in this post: find client-tool installations, then assess which of them ever talk to servers or networks you do not control.
CVE-2026-114949, CVE-2026-114950 and CVE-2026-114951: Replication, Optimizer, Logging (7.2 High each)
| CVE | Component | Privilege | Impact (CVSS) | Credit |
|---|---|---|---|---|
| CVE-2026-114949 | Server: Replication | High (PR:H) | C:H, I:H, A:H, described as takeover of MySQL Server and MySQL Cluster | None credited |
| CVE-2026-114950 | Server: Optimizer | High (PR:H) | C:H, I:H, A:H, described as takeover of MySQL Server and MySQL Cluster | Frank Wu |
| CVE-2026-114951 | Server: Logging | High (PR:H) | C:H, I:H, A:H (same scoring profile in Oracle's matrix) | None credited |
What PR:H means. In Oracle's matrix, a high-privileged attacker is one holding administrative-level rights on the database server. Oracle does not name the specific privilege. In practice this is the realm of the superuser and of accounts holding powerful global privileges such as those used to change system variables, manage replication or administer the binary log.
Who realistically exploits an administrator-only bug. Not an anonymous internet attacker. The realistic cases are an attacker who has already obtained an admin credential (reused or leaked passwords, secrets in application config, a compromised DBA workstation), a malicious insider, or a chain in which an application-level flaw such as SQL injection is first used to reach admin-level statements. For these cases the value of the bug is escalation: it turns database administrator access into a deeper compromise of the server process and its data.
Component background (context, not root cause).
- Replication covers the machinery that copies changes between servers: the receiver and applier threads on a replica and the binary log stream from a source. An administrator-level user can configure channels, change replication variables and start or stop threads.
- Optimizer covers how the server parses a query and chooses an execution plan. A high-privileged user can alter optimizer-related variables and optimizer hints, and can run complex statements.
- Logging covers the error, general, slow-query and audit log paths, whose behavior an administrator can change at runtime.
Oracle has not said that any of these features is the vulnerable behavior. The component labels tell us where to look for exposure, not what the flaw is.
CVE-2026-114953: Replication (6.5 Medium)
| Field | Detail |
|---|---|
| Component | Server: Replication |
| Privilege required | Low (PR:L): any valid account that can reach the affected code |
| Impact | Availability High only: a hang or frequently repeatable crash (complete denial of service) of MySQL Server and MySQL Cluster |
| Credit | None credited |
This is the quietest of the six but not harmless. A low-privileged account is often available to many application users, and a repeatable crash of a primary or replica is an outage. In a replicated topology the consequences compound: a crashed replica falls behind, a crashed source triggers failover, and repeated crashes can keep a cluster unstable. Because it needs only a low-privileged account, any environment that exposes database accounts to untrusted users should treat it as the most reachable of the five authenticated bugs.
CVE-2026-127428: GIS (7.1 High)
| Field | Detail |
|---|---|
| Component | Server: GIS (spatial data types and functions) |
| Privilege required | Low (PR:L) |
| Impact | Availability High (hang or frequently repeatable crash) and Confidentiality Low (unauthorized read access to a subset of accessible data) |
| Credit | Dhanush Arvind. The same researcher is credited for CVE-2026-127413 in the same update. |
| CVE ID reserved | November 12, 2026 |
GIS is the part of the server that implements spatial types and the functions that work on them. Spatial functions are ordinary SQL, so any account allowed to run SELECT statements may be able to reach them. That fits the low-privilege requirement. A crash combined with a small data-read impact is a pattern often seen with memory-handling or resource-handling defects, but Oracle gives no root cause and we do not claim one.
Where each CVE sits in MySQL
The Rest of the November MySQL Update
The six CVEs above are only part of what Oracle fixed for MySQL on November 17. The full MySQL risk matrix has ten entries, and the two highest-scored ones are not in the usual shortlist. Teams that triage from a list of "the five or six noisy CVEs" can miss them.
| CVE | Product / component | Unauthenticated remote | CVSS | Note |
|---|---|---|---|---|
| CVE-2026-115557 | MySQL Shell 26.10.0 · Shell: Core Client (Python) · HTTP | Yes | 9.8 | Highest MySQL score in the update. Per the CVE record it comes from the bundled Python runtime; the same CVE scores 7.4 in Oracle Database because attack complexity differs. Not in the six. |
| CVE-2026-114952 | MySQL Server / Cluster · Client programs · MySQL Protocol | Yes | 9.1 | In the six. The only unauthenticated Server/Cluster issue scored Critical. |
| CVE-2026-92392 | MySQL Server / Cluster · Server: Packaging (curl) · HTTP/2 | Yes | 8.1 | Bundled third-party library; attack complexity high. Not in the six. |
| CVE-2026-114949 | Server: Replication | No (admin) | 7.2 | In the six. |
| CVE-2026-114950 | Server: Optimizer | No (admin) | 7.2 | In the six. |
| CVE-2026-114951 | Server: Logging | No (admin) | 7.2 | In the six. |
| CVE-2026-127428 | Server: GIS | No (low-privileged) | 7.1 | In the six. |
| CVE-2026-114953 | Server: Replication | No (low-privileged) | 6.5 | In the six. |
| CVE-2026-114122 | MySQL Workbench 26.10.0 · Electron component | No | 3.9 | Desktop client. Not in the six. |
| CVE-2026-114948 | MySQL Cluster · Cluster: JS module | No | 2.5 | Not in the six. |
Oracle states that three of the ten patches are exploitable without authentication: CVE-2026-115557, CVE-2026-114952 and CVE-2026-92392. Of those three, only CVE-2026-114952 is in the list this post covers. If your MySQL Shell or MySQL Workbench 26.10.0 installations sit on administrator laptops or jump hosts, they deserve the same inventory pass as the server estate.
Exploit Maturity Assessment
Exploit Status
- No publicly confirmed exploit or in-the-wild exploitation identified as of November 19, 2026
- Theoretical
- PoC Available
- Functional Exploit
- Weaponized (in the wild)
| Attribute | Assessment |
|---|---|
| Exploit Availability | None publicly identified |
| Source of Exploit | None identified. Oracle has not publicly disclosed the root cause. |
| CISA KEV | Not listed for any of the six at time of writing (see the catalog) |
| CISA SSVC (CVE-2026-114952) | Exploitation: none, automatable: yes, technical impact: total (CISA ADP, assessed November 17, 2026; see the CVE record) |
| Reliability | Not applicable yet |
Proof of Concept (PoC)
No public proof of concept, exploit code or in-the-wild exploitation was identified for any of the six CVEs as of November 19, 2026. Oracle has not publicly disclosed the root cause or trigger conditions.
Time-to-Exploit Analysis
| Interval | Duration | Notes |
|---|---|---|
| Pre-release announcement → patches | 5 days (Nov 12 → Nov 17) | Oracle states it publishes a pre-release announcement on the Thursday before each CSPU |
| Disclosure → public PoC | None identified as of Nov 19 (2 days) | No exploit code found |
| Disclosure → exploitation in the wild | Not observed as of Nov 19 | No reports, not in KEV |
| Fix released → publicly diffable fix | Unknown | The affected ranges include the newest community releases found, so this clock may not have started |
| Risk Interpretation | No exploitation timeframe is estimated here, because there is no evidence or established methodology for one. Re-assess when fixed builds become publicly available for your platform, when a public PoC appears, or when exploitation is reported. | |
Vulnerability Timeline
| Event | Date |
|---|---|
| MySQL Server 8.0 reaches end of life | April 2026 |
| October 2026 Critical Patch Update: 98 new MySQL patches, 29 exploitable without authentication | October 20, 2026 |
| CVE-2026-114952 identifier reserved | October 22, 2026 |
| CSPU pre-release announcement; CVE-2026-127428 identifier reserved | November 12, 2026 |
| November 2026 CSPU released; the six CVEs published | November 17, 2026 |
| Public PoC released | Not identified as of November 19, 2026 |
| Exploitation in the wild began | Not observed as of November 19, 2026 |
| Next Critical Security Patch Update | December 15, 2026 |
| Next Critical Patch Update (quarterly) | January 19, 2027 |
Affected Versions
| Product | Affected | Fixed In | Notes |
|---|---|---|---|
| MySQL Server 8.4 (LTS) | 8.4.0 to 8.4.13 | Not published | 8.4.13 is the latest community release found, and it is inside the affected range |
| MySQL Server 9.7 (LTS) | 9.7.0 to 9.7.4 | Not published | 9.7.4 is inside the affected range |
| MySQL Server 26.10 | 26.10 | Not published | Year-based release series |
| MySQL Cluster (NDB) | 8.0.0 to 8.0.50; 8.4.0 to 8.4.13; 9.7.0 to 9.7.4; 26.10 | Not published | A separate product from MySQL Server. MySQL NDB Cluster 8.0 remains available until May 2027, whereas standard MySQL Server 8.0 is end of life. It is the only product in the advisory with an 8.0 range. |
| MySQL Server 8.0 (standard server) | Not listed (end of life since April 2026) | None expected | Not listed does not mean not affected. Oracle states unsupported releases are not tested and are "likely" affected by issues in newer ones. |
| Client-only installs (tools from the above releases) | Requires assessment | Not published | CVE-2026-114952 is attributed to the component "Client programs". Oracle does not name the affected executables, so these installs are to be assessed, not assumed vulnerable. |
| Distribution packages, containers, managed database services | Follow upstream ranges | Vendor-specific | Wait for each vendor's own advisory; do not assume parity with Oracle's dates |
Oracle lists the patches in a Patch Availability Document for MySQL (My Oracle Support document CPU440). Patches released through the CSPU program are provided only for product versions covered by Premier or Extended Support under Oracle's Lifetime Support Policy.
Active Exploitation & Threat Actors
| Question | Status |
|---|---|
| Exploitation observed in the wild | No reports as of November 19, 2026 |
| CISA KEV status | Not listed at time of writing |
| Associated threat actors | None |
| Likely first movers | Not established. No attacker activity has been reported for these CVEs. |
| Expected targeting | Not established. For context, internet-exposed database ports are common scanning targets in general. |
| What would change this | A public patch diff, a published PoC, a KEV listing, or a spike in scanning on 3306. Oracle itself warns that attackers periodically exploit vulnerabilities for which patches already exist. |
Post-Exploitation Details
These rows describe what a successful attacker generally does against a MySQL server. They are general database post-compromise behaviors, not observed activity for these CVEs, since none has been reported.
| Aspect | Assessment |
|---|---|
| Privilege Escalation | The three PR:H CVEs are scored for full server compromise from an admin account, so their role is escalation within the database. Whether they reach the operating system is not stated by Oracle. |
| Lateral Movement | Possible through replication trust (source and replica credentials), application secrets stored in tables, and backup or batch jobs that hold database credentials |
| Persistence | New privileged accounts, events and triggers, modified grants, changed authentication plugins, and plugin or component installs where the server allows it |
| Data Exfiltration | Likely objective. Dumps, bulk SELECT, binary-log streaming by a user with replication privileges. CVE-2026-114952 is scored for High confidentiality impact on its own. |
| Data Tampering | CVE-2026-114952 and the three PR:H CVEs carry High integrity impact: silent modification of business data is in scope |
| Availability Impact | CVE-2026-127428 and CVE-2026-114953 can hang or repeatedly crash the server; the three PR:H CVEs are scored for availability loss as well |
| Behavior to expect | Unusual administrative statements, new accounts, large result sets or dumps at odd hours, repeated server restarts, replication errors, and client tools opening connections to servers outside the approved list |
MITRE ATT&CK Mapping
No attacker activity has been observed for any of the six CVEs, and neither Oracle nor any published threat reporting documents an ATT&CK technique for them. The table lists all 14 Enterprise ATT&CK tactics and marks techniques as N/A until activity is documented. The notes describe what Oracle's CVSS vectors state, not observed behavior.
| Tactic | Technique | ID | Note |
|---|---|---|---|
| Reconnaissance | N/A | N/A | No technique established. |
| Resource Development | N/A | N/A | No technique established. |
| Initial Access | N/A | N/A | No technique established. Oracle scores CVE-2026-114952 as network-reachable without credentials and the other five as requiring a valid account (low-privileged or administrative). |
| Execution | N/A | N/A | No technique established. Oracle does not state code execution for any of the six. |
| Persistence | N/A | N/A | No technique established. |
| Privilege Escalation | N/A | N/A | No technique established. CVE-2026-114949, CVE-2026-114950 and CVE-2026-114951 are scored C:H, I:H, A:H from an administrative account. |
| Defense Evasion | N/A | N/A | No technique established. |
| Credential Access | N/A | N/A | No technique established. |
| Discovery | N/A | N/A | No technique established. |
| Lateral Movement | N/A | N/A | No technique established. |
| Collection | N/A | N/A | No technique established. Oracle scores confidentiality impact High for CVE-2026-114952 and Low (partial read) for CVE-2026-127428. |
| Command & Control | N/A | N/A | No technique established. |
| Exfiltration | N/A | N/A | No technique established. |
| Impact | N/A | N/A | No technique established. Oracle scores integrity impact High for CVE-2026-114952 and the three administrator-level CVEs, and availability impact High for CVE-2026-127428, CVE-2026-114953 and the three administrator-level CVEs. |
Vulnerability Chaining Opportunities
Can these be chained? Yes, with other weaknesses. Five of the six need an account first, so the realistic risk is a chain where an unrelated weakness supplies the foothold and one of these bugs deepens the compromise.
| Chain | Enabler | Outcome |
|---|---|---|
| SQL injection + PR:H CVE | An application flaw that lets an attacker run administrative statements or reach an admin-scoped connection | Escalation from application-level access to server-level compromise |
| Leaked database credentials + any authenticated CVE | Passwords in repos, backups, .env files, shared DBA accounts | Direct use of CVE-2026-127428 or CVE-2026-114953 for outage, or PR:H bugs for takeover |
| Exposed 3306 / 33060 + weak credentials | Database port reachable from untrusted networks, wildcard host accounts | Remote account acquisition, then any of the five authenticated bugs |
| Hypothetical only: CVE-2026-114952 and client-tool hosts | Not established. Oracle has not disclosed the attack path, so no enabling condition can be stated. | Not established; the scored impact is High confidentiality and integrity |
| DoS bug + replicated topology | CVE-2026-114953 or CVE-2026-127428 against a primary or a replica | Failover storms, replication lag, repeated restarts |
Patch / Mitigation
| Item | Detail |
|---|---|
| Patch Available | Yes, through Oracle's patch channel. Fixed community version numbers were not published at time of writing. |
| Patch Source | Oracle Critical Security Patch Update Advisory, November 2026 and the MySQL Patch Availability Document (My Oracle Support, CPU440) |
| Oracle's stated workaround | Generic only: block the network protocols an attack requires, and remove privileges from users who do not need them. Both may break applications; neither corrects the underlying problem. No CVE-specific workaround is published. |
| Important caveat | Upgrading to the newest community release found (8.4.13, 9.7.4, 26.10) does not move you out of the affected range. Confirm fix status in your vendor's notes before closing a ticket. |
| End of life | Standard MySQL Server 8.0 is end of life (Oracle Sustaining Support since April 21, 2026) and is not covered by these patches. MySQL NDB Cluster 8.0 is a separate product that remains available until May 2027 and appears in Oracle's affected-version matrix. Plan the move of MySQL Server 8.0 to 8.4 LTS. |
Vendor and distribution status
Status as reported on November 18, 2026 for CVE-2026-114952. Distribution trackers change quickly, so check each vendor's own page before relying on this table.
| Source | Package or version | Reported status |
|---|---|---|
| Oracle | MySQL Server 8.4, 9.7, 26.10; MySQL Cluster | Fix delivered through My Oracle Support (CPU440) |
| Public MySQL source | Community releases | Newest tags reported as 8.4.13, 9.7.4 and 26.10.0, the same versions listed as affected |
| Ubuntu | mysql-8.0, mysql-8.4, mysql-9.7 | Needs evaluation |
| Ubuntu | mysql-5.7 (16.04, 18.04) | Ignored, no upstream support |
| Debian | MySQL and MariaDB packages | No package status yet |
| Red Hat | MySQL module streams | No public CVE data yet |
| NVD | CVE record | Received; analysis pending |
"Needs evaluation" and "ignored" describe a vendor's triage state, not a finding that a package is safe or vulnerable. For the other five CVEs we found no distribution statements as of November 19.
Inventory: find every in-scope host and assess client-only installs
# Linux: server and client packages rpm -qa | grep -i mysql dpkg -l | grep -i mysql mysql --version mysqldump --version # MySQL Shell is a separate product (26.10.0 is affected by a different CVE, CVE-2026-115557) mysqlsh --version # Containers and CI images that carry client tools docker run --rm --entrypoint mysql <image> --version # macOS (Homebrew) brew list --versions | grep -i mysql # Windows (PowerShell): servers, Shell, Workbench Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object DisplayName -like "*MySQL*" | Select-Object DisplayName, DisplayVersion
-- On a running server SELECT VERSION(); -- Who holds the powerful privileges the PR:H bugs imply SELECT GRANTEE, PRIVILEGE_TYPE FROM information_schema.USER_PRIVILEGES WHERE PRIVILEGE_TYPE IN ('SUPER','SYSTEM_VARIABLES_ADMIN','REPLICATION_SLAVE_ADMIN', 'REPLICATION SLAVE','BINLOG_ADMIN','CONNECTION_ADMIN'); -- Accounts that can log in from any host SELECT user, host FROM mysql.user WHERE host IN ('%', ''); -- Replication state (8.4 and later use REPLICA wording) SHOW REPLICA STATUS\G
Interim mitigation while fixed builds are being obtained
# Network: allow database ports only from the application and admin subnets that need them # 3306 (classic protocol) and 33060 (X protocol, if the X plugin is enabled) # Server: refuse unencrypted client connections [mysqld] require_secure_transport = ON # Clients (backup, migration, admin hosts): general hardening, verify the server identity, not just encrypt mysql --ssl-mode=VERIFY_IDENTITY --host db.example.internal ... mysqldump --ssl-mode=VERIFY_IDENTITY ...
Indicators of Compromise (IOCs)
IOCs Available: No. No IP addresses, domains, file hashes, URLs or exploit artifacts have been published for any of the six CVEs, which is consistent with there being no known exploitation. The signals below are general suspicious-activity indicators for MySQL estates, not CVE-specific indicators of compromise. Treat any "IOC list" for these CVEs that appears in the next days as unverified until a primary source backs it.
| Indicator Type | What to look for | Classification |
|---|---|---|
| Server stability | Error-log lines such as got signal or Assertion failure, unexpected restarts of mysqld, restart loops under systemd | General operational signal; ordinary faults also cause it |
| Privilege use | Administrative statements from accounts that do not normally issue them, new accounts, changed grants, privilege use outside change windows | General suspicious database activity; it does not by itself indicate exploitation of any of these CVEs |
| Client behavior | mysql, mysqldump, mysqlbinlog or mysqlsh connecting to servers that are not on the approved list | General hygiene signal; not CVE-specific |
| Network | Connections to TCP 3306 or 33060 from untrusted sources; many failed logins followed by a success | General suspicious network activity |
| Data movement | Unusually large dumps or result sets, binary-log streaming by unexpected hosts | General suspicious database activity |
| Replication | Unexpected replication errors, channel changes, replicas that suddenly lag or disconnect | General operational signal |
Detection & Monitoring
Log sources
| Log Source | Key Data | Default? | Detects |
|---|---|---|---|
| MySQL error log | Crash signals, assertion failures, startup and shutdown lines, replication errors | Yes | Crash and restart patterns for the DoS bugs; replication faults |
| systemd journal / Windows Event Log | Service exit and restart events for the MySQL service | Yes | Restart loops |
| Audit log (Enterprise Edition feature or equivalent) | Logins, administrative statements, account and grant changes | No | Privilege abuse for the PR:H bugs; new accounts |
| General query log (sampling only; heavy) | Every statement | No | Short-term forensic capture when a specific host is suspected |
| Firewall / flow logs | Connections to 3306 and 33060 | Partial | Exposed database ports; client hosts reaching unapproved servers |
| EDR process and network telemetry | Which process opened which connection | Partial | MySQL client tools connecting outward |
| Performance Schema | Statement history, connection attributes | Partial | Recent statements per session without full logging |
Splunk
# ── QUERY 1: mysqld crash signatures in the error log ──────────────────── index=linux (sourcetype="mysql:error" OR source="*mysqld*" OR source="*mysql*error*") ("got signal" OR "Assertion failure") | bin _time span=15m | stats count AS crash_events by _time host | where crash_events >= 1 # ── QUERY 2: service restart loops under systemd ───────────────────────── index=linux sourcetype=syslog ("mysqld.service" OR "mysql.service") ("Main process exited" OR "Failed with result" OR "Scheduled restart job") | bin _time span=30m | stats count AS restarts by _time host | where restarts > 2 # ── QUERY 3: general hygiene hunt, admin-account activity outside business hours (adjust field names) ─ index=mysql_audit user IN ("root","admin","dba_*") | eval hour=tonumber(strftime(_time,"%H")) | where hour < 7 OR hour > 20 | stats count values(ip) AS src_ip values(command_class) AS cmds by user host # ── QUERY 4: connections to database ports that are not approved servers ─ index=firewall dest_port IN (3306,33060) action=allowed | lookup approved_mysql_servers dest_ip OUTPUT dest_ip AS approved_ip | where isnull(approved_ip) | stats count dc(dest_ip) AS targets values(dest_ip) AS dest by src_ip
Elastic / KQL
# ── mysqld crash signatures ─────────────────────────────────────────────── event.dataset:"mysql.error" and message:("got signal" or "Assertion failure") # ── MySQL client tools opening connections (EDR network events) ─────────── event.category:network and process.name:(mysql or mysqldump or mysqlbinlog or mysqlsh) and destination.port:(3306 or 33060) and not destination.ip:(<approved server IPs>) # ── inbound connections to database ports from outside the app subnets ──── destination.port:(3306 or 33060) and network.direction:inbound and not source.ip:(<app and admin subnets>)
Microsoft Sentinel (KQL)
// ── mysqld crash signatures (Linux syslog) ─────────────────────────────── Syslog | where ProcessName has "mysqld" and SyslogMessage has_any ("got signal", "Assertion failure") | summarize Crashes = count() by Computer, bin(TimeGenerated, 15m) // ── MySQL client tools connecting to unapproved servers (Defender for Endpoint) ─ let approved = dynamic(["10.0.0.10", "10.0.0.11"]); DeviceNetworkEvents | where InitiatingProcessFileName in~ ("mysql", "mysqldump", "mysqlbinlog", "mysqlsh") | where RemotePort in (3306, 33060) | where RemoteIP !in (approved) | project Timestamp, DeviceName, InitiatingProcessFileName, RemoteIP, RemotePort
Suricata (network)
alert tcp $HOME_NET any -> !$MYSQL_APPROVED_SERVERS 3306 (msg:"MySQL client connection to non-approved server"; flow:to_server,established; threshold:type limit, track by_src, count 1, seconds 300; classtype:policy-violation; sid:9261201; rev:1;) alert tcp !$APP_AND_ADMIN_SUBNETS any -> $MYSQL_SERVERS [3306,33060] (msg:"Inbound MySQL connection from outside approved subnets"; flow:to_server; flags:S; threshold:type both, track by_src, count 5, seconds 60; classtype:attempted-recon; sid:9261202; rev:1;)
Behavioral indicators for EDR
mysqldspawning a shell or an unexpected child process.- MySQL client tools run by service accounts that do not normally run them, or run on hosts that are not backup, migration or admin hosts.
- New files in the MySQL plugin directory, or unexpected plugin or component installs.
- Reads of MySQL configuration files, option files holding passwords, or the data directory by processes other than
mysqldand approved backup agents.
Risk Assessment
The table gives qualitative ratings based on Oracle's CVSS vectors, privilege requirements and the absence of identified exploitation. It does not use numerical likelihood estimates, because no validated methodology or exploitation data exists for these CVEs yet. The patch targets are SecPod recommendations for planning, not predictions.
| CVE | Risk | Rationale | Recommended target after fixed builds reach you |
|---|---|---|---|
| CVE-2026-114952 | Critical | No credentials, low complexity, High confidentiality and integrity impact. Oracle does not name the affected client executables, so client-only installs need assessment. No exploit identified. | 72 hours for database servers reachable from untrusted networks; 7 days elsewhere, once client-only installs have been assessed |
| CVE-2026-114949, CVE-2026-114950, CVE-2026-114951 | High, conditional | Scored for full server compromise, but need an administrative account. Risk rises with shared or weak admin credentials and with any SQL-injection exposure. | 7 days if admin accounts are shared or externally reachable; 14 days otherwise |
| CVE-2026-127428 | High, conditional | Low privileges are enough for a hang or crash plus a partial data read. Higher where untrusted users hold database accounts. | 7 days if untrusted users hold accounts; 14 days otherwise |
| CVE-2026-114953 | Medium | Low privileges are enough for a repeatable hang or crash. No confidentiality or integrity impact. | 14 to 30 days; sooner on multi-tenant or replicated primaries |
| Overall | High | One Critical item with an unauthenticated route, four conditional Highs, one Medium. No exploitation. Fixes arrive through Oracle's channel rather than the newest community release. | Re-score when a public diff, PoC or KEV entry appears |
Exposure decision flow
Remediation Recommendations
mysql, mysqldump and mysqlbinlog) using the commands above, record their versions, and assess them against Oracle's guidance and your vendor's fix information. They are routinely left out of database patch plans. The aim is to know they exist, not to assume they are vulnerable.%), rotate shared DBA credentials, and make sure application accounts hold only the privileges the application uses.require_secure_transport=ON on servers and run backup, migration and admin client tools with --ssl-mode=VERIFY_IDENTITY. This is general database hardening, not a CVE-specific control. Oracle has not disclosed the attack path for CVE-2026-114952, and nothing here is claimed to prevent any of the six CVEs.SecPod Coverage
| Capability | Coverage for the November 2026 MySQL CVEs |
|---|---|
| Vulnerability Detection | OVAL-based checks identifying MySQL Server and MySQL Cluster installations in the affected ranges (8.4.x, 9.7.x, 26.10) on Windows, macOS and Linux, client-tool installations for assessment, and detection of end-of-life MySQL Server 8.0 installations |
| Patch Assessment | Saner identifies hosts running affected MySQL builds and flags them for remediation once fixed builds are available from the vendor |
| Remediation | Patch deployment for supported MySQL installations via Saner as vendor fixes are released; end-of-life migration advisory workflow for MySQL 8.0 |
| CVE | Component | CVSS 3.1 |
|---|---|---|
| CVE-2026-114949 | Server: Replication | 7.2 High |
| CVE-2026-114950 | Server: Optimizer | 7.2 High |
| CVE-2026-114951 | Server: Logging | 7.2 High |
| CVE-2026-114952 | Client programs | 9.1 Critical |
| CVE-2026-114953 | Server: Replication | 6.5 Medium |
| CVE-2026-127428 | Server: GIS | 7.1 High |
Key Takeaways
- One of the six is Critical. "Critical" is in the name of Oracle's update program, not in the scores. CVE-2026-114952 is 9.1; three are 7.2 and need an administrator; CVE-2026-127428 is 7.1; CVE-2026-114953 is 6.5.
- The unauthenticated one is in a client-side component. Oracle lists it only as "Client programs" and names no executables, so client-tool installations need assessment, not an assumption of exposure.
- Five of six need an account first. Credential hygiene, port restriction and SQL-injection exposure decide how reachable they are.
- The latest community releases are still in the affected ranges. Upgrading to "latest" is not enough; confirm fix status through Oracle's patch channel or your vendor.
- Oracle has not publicly disclosed root cause or trigger, and no public PoC was identified. Treat any claimed exploit or IOC list as unverified, and re-assess when fixed builds become publicly comparable.
- This component is not new. Oracle's October update also fixed several "Client programs" issues, so client-tool hosts deserve a standing place in database patch inventories.
- Do not stop at the six. The same update carries a 9.8 in MySQL Shell and an 8.1 in a bundled library, both exploitable without authentication.
The six MySQL CVEs in Oracle's November update are a good example of why severity labels travel badly. A program name turned into a headline, and a mixed set of one Critical, four High and one Medium became "critical MySQL CVEs". The practical response is more precise than the headline: assess every host that carries MySQL client tools, shrink the number of people and networks that can reach your databases, audit privileged accounts, and apply Oracle's fixes as soon as they reach your platform.
Instantly Fix Risks in Endpoints & Cloud with Saner
Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.




