How do I check whether I am affected by CVE-2026-101800?

- Run `SELECT VERSION();` on the MySQL server and compare against the affected ranges: 8.4.0 to 8.4.12, 9.7.0 to 9.7.3, 26.7.0 to 26.7.1 for MySQL Server; 8.0.0 to 8.0.49, 8.4.0 to 8.4.12, 9.7.0 to 9.7.3, 26.7.0 to 26.7.1 for MySQL Cluster - Check for non-admin accounts with network access: `SELECT user, host FROM mysql.user;`

What is the fix for CVE-2026-101800?

- Upgrade MySQL Server or MySQL Cluster to a release after the affected ranges listed above (the fixed version numbers are unknown from the sources) - Until patched, limit low-privileged accounts to the minimum grants and restrict network access to the database port

Who is not affected by CVE-2026-101800?

Not affected if: no-low-privilege-accounts, unaffected-version.

Live › vulnerability › CVE-2026-101800

Go to dashboard

medium6.8Package

MySQL Server: privileges flaw lets low-privileged users change or read critical data

A flaw in the MySQL Server privileges component lets a low-privileged account over the network create, change or delete data it should not reach, and read critical data. Exploiting it is difficult, and the CVSS score is 6.8 with high confidentiality and integrity impact.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

6.8

medium

scored by [email protected]

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 22, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is medium, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Yes.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker with low-privilege account reads or alters critical database data.
CVSS said: 6.8. The facts above agree.

Who is affected

Teams running MySQL Server or MySQL Cluster in the affected version ranges that accept network connections from users with ordinary, low-privileged accounts. Systems on unaffected versions, or with no untrusted low-privileged accounts reachable over the network, face a smaller risk.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-101800

Go to dashboard

medium6.8Package

MySQL Server: privileges flaw lets low-privileged users change or read critical data

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

6.8

medium

scored by [email protected]

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 22, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is medium, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Yes.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker with low-privilege account reads or alters critical database data.
CVSS said: 6.8. The facts above agree.

Who is affected

Know the next one before it finds you.

Add to Slack

MySQL Server: privileges flaw lets low-privileged users change or read critical data

Why it is medium, and not just CVSS

Who is affected

Know the next one before it finds you.

MySQL Server: privileges flaw lets low-privileged users change or read critical data

Why it is medium, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources