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-101802 Overview
CVE-2026-101802 is a denial of service vulnerability in the Parser component of Oracle MySQL Server and MySQL Cluster. The flaw allows a low-privileged attacker with network access to cause a hang or repeatable crash, resulting in complete loss of database availability. Oracle disclosed the issue in the October 2026 Critical Patch Update. The vulnerability is classified under [CWE-284: Improper Access Control] and affects multiple supported release trains across both MySQL Server and MySQL Cluster. Exploitation requires only valid low-level credentials and network reachability over supported MySQL protocols, which places internet-facing or multi-tenant database deployments at elevated risk.
Critical Impact
An authenticated attacker can trigger a complete denial of service against MySQL Server and MySQL Cluster instances, disrupting applications that depend on the database tier.
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 - CVE-2026-101802 published to NVD as part of the Oracle Critical Patch Update October 2026
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-101802
Vulnerability Analysis
The vulnerability resides in the MySQL Server Parser component, which is responsible for processing SQL statements submitted by clients. A crafted query or sequence of statements causes the Parser to enter a hang state or crash the server process. Because the fault occurs during statement parsing, the attack does not require data access rights beyond basic authenticated connectivity. The impact extends to both standalone MySQL Server deployments and distributed MySQL Cluster installations, since both share the affected parsing logic.
The vulnerability affects availability only; confidentiality and integrity of stored data are not directly impacted. However, repeated crashes can disrupt dependent applications, cause transaction loss on improperly configured clients, and complicate recovery in replicated topologies. The issue is reachable through multiple MySQL protocols, broadening the exposure surface beyond the default client protocol.
Root Cause
The root cause is improper access control [CWE-284] within the Parser subsystem. Specific technical details have not been disclosed by Oracle, consistent with the vendor's standard Critical Patch Update disclosure policy. Based on the CWE classification and the Parser locus, the defect likely involves insufficient validation of statement constructs that are reachable by low-privileged sessions.
Attack Vector
An attacker needs network access to the MySQL service and valid low-privileged credentials. No user interaction is required, and exploitation complexity is low. The attacker establishes a session over a supported MySQL protocol and submits the triggering input to the Parser, producing a hang or crash. In clustered deployments, repeated triggering can propagate availability loss across nodes handling client traffic.
No public proof-of-concept code is available for CVE-2026-101802 at the time of publication. Refer to the Oracle Critical Patch Update October 2026 advisory for the authoritative description.
Detection Methods for CVE-2026-101802
Indicators of Compromise
- Unexpected mysqld process crashes or restarts recorded in the MySQL error log without correlating administrative actions
- Repeated client disconnects or connection timeouts coinciding with specific authenticated sessions
- MySQL Cluster data node failovers triggered by SQL node (mysqld) termination rather than hardware or network faults
Detection Strategies
- Monitor MySQL error logs for recurrent signal 11 or assertion failures tied to parser routines
- Enable the MySQL general query log or audit log on exposed instances to capture statement patterns preceding crashes
- Correlate authenticated session identifiers with service-availability alerts to identify a specific actor triggering restarts
Monitoring Recommendations
- Alert on MySQL server uptime resets and process-restart counters exported through Prometheus mysqld_exporter or equivalent telemetry
- Track per-user query failure rates and connection churn to surface low-privileged accounts exhibiting abnormal patterns
- Forward MySQL audit and error logs to a centralized analytics platform for cross-host correlation of parser-related failures
How to Mitigate CVE-2026-101802
Immediate Actions Required
- Apply the fixes delivered in the Oracle Critical Patch Update October 2026 to all affected MySQL Server and MySQL Cluster deployments
- Inventory MySQL instances to confirm whether running versions fall within the affected ranges listed above
- Restrict network reachability of MySQL ports to known application hosts and administrative subnets
- Review and prune low-privileged database accounts, removing unused credentials that could be leveraged for authenticated exploitation
Patch Information
Oracle addressed CVE-2026-101802 in the Oracle Critical Patch Update October 2026. Upgrade MySQL Server to a release later than 8.4.12, 9.7.3, or 26.7.1 as published in the advisory. Upgrade MySQL Cluster past 8.0.49, 8.4.12, 9.7.3, or 26.7.1 according to the deployed train. The EPSS score at publication is 0.393% (percentile 32.348), indicating low near-term predicted exploitation; however, authenticated DoS flaws remain attractive to insider and compromised-credential scenarios.
Workarounds
- Enforce network segmentation and firewall rules so only trusted application tiers can reach MySQL protocol ports
- Require TLS and strong authentication, and rotate credentials for low-privileged accounts that cannot be removed
- Implement query timeout settings and connection resource limits per user to reduce the blast radius of a parser hang
- Deploy database activity monitoring to alert on and terminate sessions producing repeated server failures
# Example: restrict a MySQL user's resource usage to limit DoS impact
ALTER USER 'app_reader'@'10.0.%'
WITH MAX_QUERIES_PER_HOUR 2000
MAX_CONNECTIONS_PER_HOUR 200
MAX_USER_CONNECTIONS 20;
# Example: bind MySQL to an internal interface and enforce firewall scope
# /etc/mysql/mysql.conf.d/mysqld.cnf
# bind-address = 10.0.10.25
# iptables -A INPUT -p tcp --dport 3306 -s 10.0.20.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

