
Read-only POSIX sh audit for CVE-2026-114952 (Oracle MySQL Server and Cluster, Client programs): judged against Oracle's affected list
Read-only audit for CVE-2026-114952, a critical flaw in the "Client programs" component of Oracle MySQL Server and MySQL Cluster, published on 2026-11-17 in Oracle's November 2026 Critical Patch Update.
Written in POSIX sh, so it runs as is on busybox ash (Alpine, Synology), on
dash and on bash. It never sends a request, never runs an exploit and never
changes anything on the host.
The tools it needs are sed, awk, grep, cat, readlink, head, tail, stat,
env, dirname and od; tr and id are not needed, so it also runs on stripped
busybox builds such as the one of VMware ESXi. If one of the eleven is missing it stops
with exit code 4 and names it.
It finds every MySQL server program on the machine (running and merely installed, containers included when their processes are visible) and the classic client programs, identifies the product (Oracle MySQL, MariaDB or a fork), judges the version against Oracle's affected list, and, for a server inside the list, reads the sockets it really listens on.
Read the next section first: the public sources are thin, and this audit says exactly where it relies on them.
What the sources state (the CVE record published by Oracle as the CVE Numbering Authority, NVD, and the CWE added by CISA):
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (no availability impact).| product | affected |
|---|---|
| MySQL Server | 8.4.0 to 8.4.13, 9.7.0 to 9.7.4, and 26.10 |
| MySQL Cluster | 8.0.0 to 8.0.50, 8.4.0 to 8.4.13, 9.7.0 to 9.7.4, and 26.10 |
What no source states, and this script does not invent:
26.10 and 26.10.N as the listed 26.10; if Oracle ships it in another
form (for example 26.10.0-1), that is read the same way, and anything that
does not parse is UNKNOWN.Oracle's own advisory (https://www.oracle.com/security-alerts/cspunov2026.html) answers HTTP 403 to command line tools, so the affected list above comes from the CVE record. Check the advisory and Oracle's patch availability document yourself.
# review it first, then run as root (other users' /proc entries need root)
sh cve-2026-114952-mysql-audit.sh
sh cve-2026-114952-mysql-audit.sh --json
sh cve-2026-114952-mysql-audit.sh --quiet # verdict only
sh cve-2026-114952-mysql-audit.sh --no-banner # text report without the banner
On a remote host, nothing is copied to disk:
ssh host 'sh -s' < cve-2026-114952-mysql-audit.sh
ssh host 'sh -s -- --json' < cve-2026-114952-mysql-audit.sh
Without root the script still runs, but it cannot read the /proc entries of a
server that runs as the mysql user: such a process is reported as unreadable and
the result is at least UNKNOWN. The banner is printed only in the text report;
--quiet and --json never print it, and it is plain ASCII with colour only on a
terminal (and not with NO_COLOR).
| exit | verdict | meaning |
|---|---|---|
| 0 | PATCHED | every instance is above the last release in Oracle's affected list (see below for what this means), or its changelog names the CVE |
| 0 | NOT_APPLICABLE | no MySQL server or client here, or every instance is MariaDB or in a train Oracle does not list |
| 1 | MITIGATED | a server inside the list that is not reachable from the network right now (not running, or only loopback and unix-socket listeners). Still update |
| 2 | VULNERABLE | a server inside the list that listens on a non-loopback address |
| 3 | UNKNOWN | cannot decide: a fork, a distribution package that may carry a backport, a container image, an unreadable process, an unparseable version, or an affected client program with no affected server. Treat as suspect |
| 4 | usage error or missing basic tools |
With several instances the worst one wins (VULNERABLE > UNKNOWN >
MITIGATED > PATCHED); NOT_APPLICABLE only when every instance is. A running
mysqld whose binary path cannot be read lowers a clean result to UNKNOWN.