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-101732 Overview
CVE-2026-101732 is a denial-of-service vulnerability in the Optimizer component of Oracle MySQL Server and MySQL Cluster. A high-privileged attacker with network access via multiple protocols can trigger a hang or repeatable crash, resulting in complete loss of database availability. The flaw is categorized under [CWE-284: Improper Access Control] and affects multiple supported release trains across both MySQL Server and MySQL Cluster. Oracle addressed the issue in the October 2026 Critical Patch Update.
Critical Impact
Successful exploitation produces a complete denial of service against MySQL Server or MySQL Cluster instances, disrupting any application dependent on the affected database.
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-101732 published to the National Vulnerability Database
- 2026-10-22 - Last updated in the NVD database
Technical Details for CVE-2026-101732
Vulnerability Analysis
The vulnerability resides in the Server: Optimizer component of Oracle MySQL. The Optimizer is responsible for parsing SQL statements and selecting execution plans. An authenticated attacker with high privileges can submit crafted queries that trigger an unhandled condition in the Optimizer. The result is a server hang or a repeatable crash that terminates the MySQL process.
Because the attack is reachable over the network using multiple MySQL protocols, any exposed instance where an attacker holds elevated database credentials can be rendered unavailable. The flaw does not expose data or allow modification. It affects availability only, but recovery requires restart and potentially cluster failover handling. The EPSS score at publication is 0.44%, reflecting a low observed exploitation probability in the wild.
Root Cause
Oracle has not published implementation-level details. The CWE-284 classification indicates improper access control within the Optimizer code path, allowing a privileged user to invoke logic that lacks sufficient boundary checks against resource exhaustion or invalid internal state. The specific trigger is held embargoed under Oracle's responsible disclosure practice.
Attack Vector
Exploitation requires network reachability to the MySQL listener and a valid high-privileged account such as a user holding administrative or schema-wide privileges. The attacker submits a malformed or edge-case query through any supported MySQL protocol. No user interaction is required. The Optimizer processes the input and enters a hang state or crashes the server process, producing a complete denial of service.
No verified proof-of-concept code is public. Refer to the Oracle Security Alert - Oct 2026 for vendor technical references.
Detection Methods for CVE-2026-101732
Indicators of Compromise
- Unexpected mysqld process termination or restart events in system logs
- Repeated client-side ERROR 2013 (HY000): Lost connection to MySQL server during query entries from a single authenticated session
- Unusual query patterns from administrative accounts preceding server unavailability
- Spikes in MySQL error log entries referencing Optimizer stack frames or assertion failures
Detection Strategies
- Correlate MySQL audit log entries from high-privileged accounts with server crash or restart timestamps
- Monitor performance_schema and error_log for abnormal query planning latency or repeated Optimizer-related errors
- Baseline normal administrative query behavior and alert on malformed statements from root, DBA, or replication accounts
- Track MySQL Cluster node failover events that lack a corresponding operational cause
Monitoring Recommendations
- Forward MySQL error logs and audit logs to a centralized SIEM for cross-session correlation
- Alert on repeated mysqld restarts within a short window across any node in a cluster
- Monitor privileged account activity, including source IP, for connections originating outside expected administrative subnets
How to Mitigate CVE-2026-101732
Immediate Actions Required
- Apply the fixes delivered in the Oracle October 2026 Critical Patch Update to all affected MySQL Server and MySQL Cluster instances
- Audit all accounts holding high privileges and revoke privileges that are not operationally required
- Restrict network exposure of MySQL listeners to trusted management subnets and application tiers only
- Verify backup and failover procedures are current so that a successful DoS does not extend recovery time
Patch Information
Oracle addressed CVE-2026-101732 in the October 2026 Critical Patch Update. Upgrade MySQL Server to a release later than 8.4.12, 9.7.3, or 26.7.1 as applicable, and MySQL Cluster to a release later than 8.0.49, 8.4.12, 9.7.3, or 26.7.1. See the Oracle Security Alert - Oct 2026 for exact fixed versions and download locations.
Workarounds
- Enforce least privilege by removing administrative grants from application and reporting accounts
- Place MySQL instances behind a bastion or jump host and block direct network access from untrusted zones
- Enable the MySQL audit plugin to record all statements issued by privileged accounts for forensic review
- Deploy connection rate limiting and query timeout controls to reduce the window of impact if a crash is triggered
# Configuration example: restrict network exposure and enable auditing
# /etc/mysql/my.cnf
[mysqld]
bind-address = 10.0.0.5
skip-name-resolve
max_connections = 200
wait_timeout = 60
plugin-load-add = audit_log.so
audit_log_policy = ALL
audit_log_format = JSON
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

