Skip to main content

MySQL Server CVE-2026-101609

| EUVDEUVD-2026-106017 MEDIUM
2026-10-20 secalert_us@oracle.com GHSA-jfxj-96mq-cxwq
4.4
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with high DB privileges
  2. Delivery
    Connect via MySQL protocol
  3. Exploit
    Send crafted InnoDB operation
  4. Execution
    Trigger hang or repeatable crash
  5. Impact
    Complete denial of service

Vulnerability Assessment

Exploitation Conditions

Exploitation requires the attacker to already possess HIGH privileges on the target MySQL Server or MySQL Cluster instance (CVSS PR:H) and network reachability over one of MySQL's supported protocols (AV:N); no end-user interaction is needed (UI:N). The flaw resides specifically in the InnoDB storage engine component. Key limiting factors: Oracle rates this 'difficult to exploit' (AC:H), meaning a reliable trigger depends on specific conditions/timing rather than a simple request; the required high-privilege authentication effectively restricts realistic abuse to already-trusted or compromised database accounts; and impact is confined to availability (hang or repeatable crash) with no confidentiality or integrity effect. Affected: MySQL Server 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1.

Impact

This is a genuinely low-priority issue despite being a CRITICAL-sounding 'complete DOS' in the description. The CVSS 3.1 base score is only 4.4 (Medium), and the vector tells the real story: AV:N (network) but AC:H (high attack complexity - Oracle explicitly calls it 'difficult to exploit') and PR:H (attacker must already hold high privileges on the MySQL Server/Cluster instance). Impact is availability-only (C:N/I:N/A:H) with no scope change (S:U) - no data disclosure, no code execution, no privilege escalation. All exploitation signals point away from urgency: no CISA KEV listing, no public POC identified, and no EPSS score was provided in the input (absence of EPSS is a data gap, not a low score - it cannot be used either way here). An SSVC-style read would be: Exploitation=none observed, Automatable=no (high-privilege precondition and high complexity defeat mass automation), Technical Impact=partial (DoS only). The combination of PR:H + AC:H means a successful attacker is almost certainly an already-trusted/authenticated database user, making this closer to an insider or post-compromise abuse case than an external threat. No conflicting signals were observed between the CVSS vector and the description - both agree on network vector, high privilege, and availability-only impact.

Exploit ScenarioDerived

An attacker who already holds high database privileges connects to the MySQL Server or Cluster over a supported network protocol and issues a specially crafted sequence that exercises a flaw in the InnoDB storage engine, driving the server into a hang or a repeatable crash that produces a complete denial of service. Because the flaw is availability-only, no data is read or altered - the payoff is downtime. No public exploit code has been identified, and the high attack complexity means a reliable trigger is non-trivial to develop.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

High-privileged authenticated users with network access can cause a hang or repeatable crash of Oracle MySQL Server or MySQL Cluster through a flaw in the InnoDB component, resulting in complete denial of service while confidentiality and integrity remain unaffected. The issue affects MySQL Server 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1, plus MySQL Cluster 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1. Oracle rates exploitation as difficult (AC:H) and requiring high privileges (PR:H); no public exploit identified at time of analysis.

RemediationAI

Use Oracle's October 2026 Critical Patch Update advisory (https://www.oracle.com/security-alerts/cpuoct2026.html) as the authoritative vendor source for the fixed MySQL Server and MySQL Cluster release; the provided data does not specify an exact fixed version, so confirm the patched version in the advisory before upgrading. Until patching is possible, restrict network access to MySQL ports to trusted application and administrative hosts, remove or tightly limit accounts with high privileges, and monitor for unexpected InnoDB hangs or restart loops. These controls reduce exposure but do not eliminate the flaw: network restriction can break legitimate clients, and least-privilege changes may disrupt administrative workflows. High-availability or failover can shorten outage duration but does not prevent the crash itself. Patch status: vendor advisory referenced; exact fix version not specified in the provided data.

Affected VersionsENISA

MySQL Cluster 8.0.0-8.0.49
MySQL Cluster 26.7.0-26.7.1
MySQL Server 26.7.0-26.7.1
MySQL Server 9.7.0-9.7.3
MySQL Cluster 9.7.0-9.7.3
MySQL Cluster 8.4.0-8.4.12
MySQL Server 8.4.0-8.4.12

Affected Packages

euvd mysql_cluster no fix
euvd mysql_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in Oracle MySQL's InnoDB storage engine and is reachable over the network via multiple protocols by an authenticated account holding high privileges. The assessed CVSS vector is CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H, meaning availability-only impact, no user interaction, and a difficult-to-exploit condition that likely depends on specific timing or state rather than a simple request. No CWE identifier was supplied, so the precise root-cause class is not formally categorized in the provided data. InnoDB handles transactional storage, locking, and crash recovery, so a flaw that triggers a hang or repeatable crash can take down the database service even though confidentiality and integrity are unaffected. No CPE strings were included; affected version ranges come from Oracle and ENISA EUVD.

Know when MySQL gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 4.4 MEDIUM
AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 4.4 MEDIUM

Network-reachable but Oracle-confirmed difficult to exploit (AC:H) and requires an existing high-privilege DB account (PR:H); impact is availability-only DoS, so C:N/I:N/A:H.

3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Red Hat 4.4 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

DescriptionNVD

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: InnoDB). Supported versions that are affected are MySQL Server: 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster: 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Ubiquitous
MySQL is one of the most widely deployed databases worldwide
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in MySQL

View all
CVE-2016-6662 CRITICAL POC
9.8 Sep 20

Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2

CVE-2012-5613 MEDIUM POC
6.0 Dec 03

MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the

CVE-2017-3599 HIGH POC
7.5 Apr 24

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity

CVE-2012-2122 MEDIUM POC
5.1 Jun 26

sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x befor

CVE-2020-5398 HIGH
7.5 Jan 17

In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,

CVE-2012-5612 MEDIUM POC
6.5 Dec 03

Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a and possibly ot

CVE-2012-5611 MEDIUM POC
6.5 Dec 03

Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53

CVE-2020-1967 HIGH POC
7.5 Apr 21

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due

CVE-2016-6664 HIGH POC
7.0 Dec 13

mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server befo

CVE-2015-3152 MEDIUM POC
5.9 May 16

Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the

CVE-2026-24479 CRITICAL POC
9.8 Jan 27

HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.

CVE-2016-2105 HIGH
7.5 May 05

Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy