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

- 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, and MySQL Cluster 8.0.0 to 8.0.49. - unknown whether any configuration check narrows exposure; the sources do not say.

What is the fix for CVE-2026-101802?

- Upgrade MySQL Server 8.4.x to a release after `8.4.12`, 9.7.x to a release after `9.7.3`, and 26.7.x to a release after `26.7.1`, per Oracle's July 2026 CPU. - Upgrade MySQL Cluster 8.0.x past `8.0.49` and the matching 8.4, 9.7 and 26.7 fixed releases.

Who is not affected by CVE-2026-101802?

Not affected if: default-config.

Live › vulnerability › CVE-2026-101802

Go to dashboard

medium6.5Package

MySQL Server parser flaw lets a low-privilege user crash the database

A flaw in the MySQL Server parser lets an authenticated low-privilege user over the network hang or repeatedly crash MySQL Server and MySQL Cluster. The attack causes denial of service only; the sources report no confidentiality or integrity loss.

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

CVSS 3.x

6.5

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: Database server hangs or crashes repeatedly, causing full denial of service.
CVSS said: 6.5. The facts above say low; we keep the sources' medium until an analyst looks.

Who is affected

Teams that run MySQL Server or MySQL Cluster on the affected version lines and accept connections from other users or networks. Single-user or non-network-exposed databases carry less risk. The sources do not name specific fixed release numbers beyond the ranges given.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-101802

Go to dashboard

medium6.5Package

MySQL Server parser flaw lets a low-privilege user crash the database

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

CVSS 3.x

6.5

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: Database server hangs or crashes repeatedly, causing full denial of service.
CVSS said: 6.5. The facts above say low; we keep the sources' medium until an analyst looks.

Who is affected

Know the next one before it finds you.

Add to Slack

MySQL Server parser flaw lets a low-privilege user crash the database

Why it is medium, and not just CVSS

Who is affected

Know the next one before it finds you.

MySQL Server parser flaw lets a low-privilege user crash the database

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