Skip to main content
Vulnerability Database/CVE-2026-101798

CVE-2026-101798: MySQL Server & Cluster DOS Vulnerability

CVE-2026-101798 is a denial of service vulnerability in MySQL Server and MySQL Cluster affecting versions 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1. Attackers can cause system crashes and service disruption. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-101798 Overview

CVE-2026-101798 affects the Oracle MySQL Server and MySQL Cluster products in the Server: Optimizer component. The flaw allows an authenticated attacker with high privileges and network access to trigger a hang or repeatable crash of the database service. Successful exploitation results in a complete denial of service (DoS) of affected MySQL instances. The vulnerability was disclosed as part of the Oracle Critical Patch Update released in October 2026. It is categorized under [CWE-284: Improper Access Control] and impacts widely deployed enterprise database versions across production environments.

Critical Impact

Authenticated attackers can cause complete denial of service of MySQL Server or MySQL Cluster instances through the query optimizer, disrupting dependent applications and services.

Affected Products

  • MySQL Server versions 8.4.0 through 8.4.12, 9.7.0 through 9.7.3, and 26.7.0 through 26.7.1
  • MySQL Cluster versions 8.0.0 through 8.0.49, 8.4.0 through 8.4.12, and 9.7.0 through 9.7.3
  • MySQL Cluster versions 26.7.0 through 26.7.1

Discovery Timeline

  • 2026-10-20 - Oracle disclosed the vulnerability in the October 2026 Critical Patch Update
  • 2026-10-20 - CVE-2026-101798 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-101798

Vulnerability Analysis

The vulnerability resides in the MySQL query optimizer, the subsystem responsible for parsing SQL statements and selecting execution plans. An authenticated attacker with high privileges can craft input that causes the optimizer to hang or crash the server process. The attack is reachable over multiple MySQL network protocols, making remote exploitation straightforward once credentials are available.

The weakness is classified under [CWE-284: Improper Access Control]. The impact is restricted to availability; confidentiality and integrity are not affected. EPSS data places the exploitation probability at 0.422 percent as of 2026-10-22, consistent with the privilege requirement for exploitation.

Root Cause

The root cause stems from improper handling within the Server: Optimizer component when evaluating certain query structures. Oracle has not published code-level details, but the behavior produces either a persistent hang or a repeatable crash of the database engine. Because the flaw is reachable through multiple protocols, any network-exposed interface to a vulnerable MySQL instance represents an exploitation path.

Attack Vector

Exploitation requires an authenticated session with high privileges on the target MySQL Server or MySQL Cluster node. The attacker submits specially crafted queries through a supported protocol. Processing of these queries triggers the hang or crash condition in the optimizer, taking the database offline. Repeated submission after service recovery produces a sustained denial of service.

No verified proof-of-concept code is published. See the Oracle Critical Patch Update October 2026 advisory for the official technical details.

Detection Methods for CVE-2026-101798

Indicators of Compromise

  • Repeated unexpected crashes or restarts of mysqld processes recorded in system logs
  • Prolonged query execution or stalled worker threads observed in SHOW PROCESSLIST output
  • Spikes in connection errors and client timeouts correlated with specific authenticated sessions

Detection Strategies

  • Audit MySQL general and error logs for repeated optimizer-related errors or segmentation faults preceded by anomalous SQL statements
  • Correlate authenticated session activity from high-privilege accounts with service restart events
  • Monitor for unusual query patterns originating from administrative accounts, including malformed or deeply nested statements

Monitoring Recommendations

  • Alert on mysqld process restarts and abnormal termination codes via infrastructure monitoring
  • Track query latency and thread state distribution for sudden increases in stalled or long-running queries
  • Enable MySQL audit logging for all high-privilege accounts and forward events to a centralized analytics platform

How to Mitigate CVE-2026-101798

Immediate Actions Required

  • Apply the October 2026 Oracle Critical Patch Update to all affected MySQL Server and MySQL Cluster instances
  • Inventory MySQL deployments and identify versions within the affected ranges, including 8.0.x Cluster builds
  • Review and reduce the number of accounts holding administrative privileges on database servers
  • Restrict network access to MySQL ports so only trusted application hosts can establish sessions

Patch Information

Oracle addressed CVE-2026-101798 in the Oracle Critical Patch Update October 2026. Administrators should upgrade MySQL Server beyond versions 8.4.12, 9.7.3, and 26.7.1, and upgrade MySQL Cluster beyond versions 8.0.49, 8.4.12, 9.7.3, and 26.7.1. Patches are available through Oracle Support and standard package distribution channels for supported platforms.

Workarounds

  • Limit high-privilege account issuance and rotate credentials for administrative users
  • Enforce network segmentation and firewall rules to restrict MySQL protocol access to a defined allowlist
  • Deploy a MySQL proxy or query firewall to inspect and rate-limit statements from privileged sessions until patches are applied
  • Enable automatic service recovery and configure clustering failover to minimize downtime from crash conditions
bash
# Configuration example: restrict network access and enforce TLS
# /etc/mysql/mysql.conf.d/mysqld.cnf
[mysqld]
bind-address = 10.0.0.10
require_secure_transport = ON
max_connections = 200
max_user_connections = 20

# Firewall allowlist (iptables)
iptables -A INPUT -p tcp --dport 3306 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 3306 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.