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

CVE-2026-101787: MySQL Server Optimizer DOS Vulnerability

CVE-2026-101787 is a denial of service vulnerability in MySQL Server and MySQL Cluster affecting the Server Optimizer component. High privileged attackers can cause complete system crashes. This article covers technical details, affected versions, impact analysis, 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-101787 Overview

CVE-2026-101787 is a denial of service vulnerability in the Oracle MySQL Server and MySQL Cluster products. The flaw resides in the Server: Optimizer component and is classified under [CWE-284: Improper Access Control]. An authenticated attacker with high privileges and network access can trigger a hang or repeatable crash of the database service. Successful exploitation results in a complete denial of service of MySQL Server and MySQL Cluster instances.

Critical Impact

Authenticated attackers can crash or hang MySQL Server and MySQL Cluster deployments remotely, disrupting database availability for 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, 9.7.0 through 9.7.3, and 26.7.0 through 26.7.1
  • Oracle MySQL deployments exposing the database service over supported network protocols

Discovery Timeline

  • 2026-10-20 - CVE-2026-101787 published to the National Vulnerability Database
  • 2026-10-20 - Oracle addresses the issue in the October 2026 Critical Patch Update
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-101787

Vulnerability Analysis

The vulnerability affects the query optimizer component of MySQL Server and MySQL Cluster. The optimizer analyzes SQL statements and selects execution plans for queries. A high-privileged authenticated user can submit crafted input through multiple protocols that triggers an unhandled condition in the optimizer. The result is either an indefinite hang of the server process or a reproducible crash that terminates the database instance.

Because the attack reaches the server over the network, remote operators with valid credentials can repeatedly invoke the condition. Each invocation forces the database to restart or hang, denying service to legitimate applications. The vulnerability does not expose data confidentiality or integrity, but it directly impacts availability.

Root Cause

The root cause maps to [CWE-284: Improper Access Control] within the optimizer code path. The optimizer accepts input from authenticated sessions without enforcing constraints that would prevent abuse by a privileged user. The condition reaches a fault state that the server cannot recover from gracefully.

Attack Vector

Exploitation requires an existing account with high privileges on the target MySQL Server or MySQL Cluster deployment. The attacker then issues a crafted request through any supported MySQL protocol to the optimizer. The server either stalls or terminates. Repeated issuance produces a sustained denial of service across the database tier.

No verified public proof of concept exists at the time of publication. The EPSS probability stands at 0.422% with a percentile of 35.4, consistent with a non-weaponized authenticated DoS flaw. See the Oracle Critical Patch Update advisory for additional detail.

Detection Methods for CVE-2026-101787

Indicators of Compromise

  • Unexpected crashes or restarts of mysqld processes recorded in the MySQL error log
  • Repeated signal 11 or assertion failure entries originating from optimizer code paths
  • Sudden spikes in failed client connections correlated with privileged account sessions
  • Prolonged query execution or server hangs tied to specific authenticated sessions

Detection Strategies

  • Audit MySQL general query log entries from high-privileged accounts and flag abnormal query patterns against the optimizer
  • Correlate database process termination events with authenticated session identifiers to identify abusive accounts
  • Monitor the MySQL error log for recurrent crash signatures with the same stack frames in optimizer functions
  • Baseline normal query latency and alert when privileged accounts generate repeated long-running or stalled queries

Monitoring Recommendations

  • Forward MySQL error logs and audit logs to a centralized log analytics or SIEM platform for correlation
  • Track database uptime, restart counts, and connection error rates as availability signals
  • Alert on administrative or replication account logins from unexpected source addresses
  • Review privileged account inventory and remove accounts that no longer require administrative access

How to Mitigate CVE-2026-101787

Immediate Actions Required

  • Apply the October 2026 Oracle Critical Patch Update to all affected MySQL Server and MySQL Cluster instances
  • Inventory accounts with high privileges and revoke access that is not operationally required
  • Restrict network access to MySQL ports so that only trusted application tiers and administrative hosts can connect
  • Enable detailed audit logging for privileged sessions until patching is complete

Patch Information

Oracle addressed CVE-2026-101787 in the October 2026 Critical Patch Update. Administrators should upgrade MySQL Server beyond 8.4.12, 9.7.3, or 26.7.1 and MySQL Cluster beyond 8.0.49, 8.4.12, 9.7.3, or 26.7.1 as published by Oracle. Full remediation details are available in the Oracle Critical Patch Update advisory.

Workarounds

  • Reduce the number of accounts holding administrative or high privileges on affected servers
  • Place MySQL instances behind network segmentation that blocks direct access from untrusted networks
  • Enforce multi-factor authentication on bastion hosts used to reach the database tier
  • Enable automatic restart supervision for mysqld to shorten outage windows while patches are deployed
bash
# Configuration example: restrict MySQL network exposure and verify version
mysql -u root -p -e "SELECT VERSION();"

# Limit bind address to trusted interface in my.cnf
# [mysqld]
# bind-address = 10.0.0.10

# Review accounts with elevated privileges
mysql -u root -p -e "SELECT user, host FROM mysql.user WHERE Super_priv='Y';"

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.