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

CVE-2026-101679: MySQL Server and Cluster DOS Vulnerability

CVE-2026-101679 is a denial of service vulnerability in MySQL Server and MySQL Cluster that allows unauthenticated attackers to cause system crashes. This post covers the technical details, affected versions, 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-101679 Overview

CVE-2026-101679 affects the Client programs component of Oracle MySQL Server and MySQL Cluster. An unauthenticated attacker with network access can exploit the flaw across multiple protocols to trigger a hang or repeatable crash. Successful exploitation results in a complete denial of service against the database engine.

The weakness is classified under [CWE-284: Improper Access Control]. Oracle disclosed the issue in the October 2026 Critical Patch Update advisory. No public exploit code is currently available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

Critical Impact

Remote unauthenticated attackers can crash or hang MySQL Server and MySQL Cluster instances, disrupting any application that depends on the affected database tier.

Affected Products

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

Discovery Timeline

  • 2026-10-20 - CVE-2026-101679 published to the National Vulnerability Database
  • 2026-10-22 - Last updated in the NVD database

Technical Details for CVE-2026-101679

Vulnerability Analysis

The vulnerability resides in the Client programs component shared by MySQL Server and MySQL Cluster. An attacker reaches the vulnerable code path over the network without authentication and without user interaction. The impact is limited to availability. Confidentiality and integrity are not affected.

Exploitation produces either a sustained hang or a repeatable crash of the database process. Because the condition is deterministically repeatable, an attacker can suppress service recovery by re-sending the triggering input after each restart. Multiple protocols are reported as viable delivery channels, which broadens the exposed attack surface for internet-facing or lateral-reachable deployments.

The underlying weakness category, [CWE-284: Improper Access Control], indicates that controls intended to restrict reachability of the vulnerable code path are insufficient. Oracle has not published root-cause code details in the advisory.

Root Cause

Oracle's advisory attributes the flaw to the Client programs component across the MySQL Server and MySQL Cluster codebase. The specific function and protocol handler have not been disclosed. Oracle categorizes the issue as easily exploitable, which indicates minimal preconditions and no required privileges.

Attack Vector

The attack vector is network-based. An unauthenticated remote attacker sends crafted traffic over one of the supported MySQL protocols to the affected service. Processing the input causes the server to hang or crash, denying service to downstream consumers. No valid credentials, session, or user interaction are required.

No verified public proof-of-concept exists. See the Oracle Security Alert - October 2026 for vendor-authoritative details.

Detection Methods for CVE-2026-101679

Indicators of Compromise

  • Unexpected mysqld process termination, segmentation faults, or restarts recorded in the MySQL error log
  • Repeated short-lived TCP connections to port 3306, 33060, or MySQL Cluster management ports from a single external source
  • Sudden client-side connection failures and replication lag across dependent application tiers
  • Abnormal spikes in protocol-level parse errors or malformed packet counters in MySQL status variables

Detection Strategies

  • Alert on repeated mysqld crash-restart cycles within a short time window using host monitoring agents or systemd watchdog telemetry
  • Correlate network flow data to identify unauthenticated sources sending repeated connection attempts to MySQL listener ports
  • Monitor MySQL error_log and audit_log outputs for abnormal termination signatures tied to protocol parsing

Monitoring Recommendations

  • Ingest MySQL error logs and host process telemetry into a centralized SIEM or data lake for correlation
  • Baseline normal client connection rates per source and alert on statistical deviations
  • Track database availability SLOs so repeated short outages trigger investigation rather than silent auto-recovery

How to Mitigate CVE-2026-101679

Immediate Actions Required

  • Apply the fixes delivered in the Oracle October 2026 Critical Patch Update to all affected MySQL Server and MySQL Cluster instances
  • Restrict network reachability of MySQL listener ports to known application tiers using firewall and security group rules
  • Prioritize patching for internet-exposed or multi-tenant database instances where the DoS impact is greatest

Patch Information

Oracle addressed CVE-2026-101679 in the Critical Patch Update released in October 2026. Patch availability, fixed versions, and upgrade guidance are documented in the Oracle Security Alert - October 2026. Upgrade MySQL Server and MySQL Cluster to a release later than the affected version ranges listed in the advisory.

Workarounds

  • Place MySQL instances behind a network segmentation boundary that denies connections from untrusted sources
  • Enforce allowlist-based access on database listener ports until patches are deployed across the fleet
  • Deploy a database proxy such as ProxySQL or MySQL Router with connection rate limiting to blunt repeated DoS attempts
  • Configure process supervision to automatically restart mysqld while availability alerts drive urgent remediation
bash
# Example: restrict MySQL listener to internal application subnet only
iptables -A INPUT -p tcp --dport 3306 -s 10.10.0.0/16 -j ACCEPT
iptables -A INPUT -p tcp --dport 3306 -j DROP

# Example: verify installed MySQL version against affected ranges
mysql --version
mysqladmin -u root -p version

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.