CVE-2026-114952: MySQL auth bypass in client programs

cve.now

4 min read Original article ↗
CVEs

CVE-2026-114952EUVD-2026-127662GHSA-CW64-JWV6-F83GPublished November 17, 2026, updated

Exploited
No known exploitation

Fix
See vendor advisory

Who is exposed
Not reported

Summary

A flaw in the client programs component of Oracle's MySQL Server and MySQL Cluster lets an attacker read, change, create, or delete critical data that these products can access. It can be reached remotely over the network without logging in, and no action from a user is needed.

Written by a model

Original description

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Client programs). Supported versions that are affected are MySQL Server: 8.4.0-8.4.13, 9.7.0-9.7.4, 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. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server, MySQL Cluster accessible data as well as unauthorized access to critical data or complete access to all MySQL Server, MySQL Cluster accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-114952 (Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Client programs).), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-114952 (entry last updated 2026-11-19):
Affected:
- Oracle Corporation MySQL Server: versions 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10
- Oracle Corporation MySQL Cluster: versions 8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-114952 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114952 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.oracle.com/security-alerts/cspunov2026.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-114952
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114952"}.

Affected versions

  • Oracle Corporation MySQL Server8.4.0-8.4.13, 9.7.0-9.7.4, 26.10

  • Oracle Corporation MySQL Cluster8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10

cve.now Index

52Pof 100 · provisional · methodology v3

  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach17/20Affects MySQL (a widely deployed server, runtime, framework or database)
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 97 if added to CISA KEV
  • Would score about 92 if CISA's SSVC rates exploitation active
  • Would score about 57 if advisories confirm default setups are exposed

How the score works · Rankings

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Posted on X by cve.now1 day
  5. Record last updated

Public exploit activity

10

Posted on X by cve.now

100%0Nov 17Nov 20

  • GitHub PoC repos: 1
  • EPSS: 0.29%
  • Posted on X by cve.now Nov 18

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 10

Evidence 4

Questions about CVE-2026-114952

Is CVE-2026-114952 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-114952?

MySQL Server: versions 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10. MySQL Cluster: versions 8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4, 26.10.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.