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-101799 Overview
CVE-2026-101799 is a denial-of-service vulnerability in the Group Replication Group Communication System (GCS) component of Oracle MySQL Server and MySQL Cluster. An unauthenticated attacker with access to the adjacent network segment can send crafted traffic that causes the database to hang or crash repeatedly. The flaw is categorized under [CWE-284: Improper Access Control] and affects multiple supported MySQL branches. Oracle addressed the issue in its October 2026 Critical Patch Update.
Critical Impact
Successful exploitation produces a complete denial of service against MySQL Server and MySQL Cluster instances, interrupting database availability for all dependent applications.
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 CVE-2026-101799 published to the National Vulnerability Database
- 2026-10-20 - Oracle releases security patch as part of the October 2026 Critical Patch Update
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-101799
Vulnerability Analysis
The vulnerability resides in the Group Replication GCS component, which handles cluster membership and message passing between MySQL nodes participating in a replication group. An attacker on the same physical communication segment as the server can send malformed GCS traffic without authenticating. Processing this traffic drives the server into a hang state or triggers a reliably repeatable crash. The impact is limited to availability; the flaw does not expose data or allow modification of stored records.
Because the attack succeeds without credentials and without user interaction, any device sharing the Layer 2 segment with a MySQL replication node can trigger the condition. Operators running MySQL on shared VLANs, co-tenant subnets, or flat cluster-interconnect networks face the greatest exposure.
Root Cause
The underlying weakness maps to [CWE-284: Improper Access Control]. The GCS layer accepts and processes group communication messages from the adjacent network without sufficient validation of the sender or message contents. This permits an unauthorized peer to influence the state machine that governs replication group membership and messaging.
Attack Vector
Exploitation requires adjacent network access, meaning the attacker must reach the MySQL node across the same broadcast domain or logical segment used for group replication traffic. No credentials are needed and no user interaction is required. The attacker transmits crafted GCS frames to the targeted node. Repeated transmission maintains the denial-of-service condition for as long as the attacker has segment access.
No verified public proof-of-concept code is available at this time. Refer to the Oracle Critical Patch Update October 2026 for authoritative technical detail.
Detection Methods for CVE-2026-101799
Indicators of Compromise
- Unexpected mysqld process restarts or crash entries in the MySQL error log referencing Group Replication or GCS modules
- Sudden cluster membership churn, with nodes repeatedly leaving and rejoining the replication group
- Spikes of malformed or unexpected traffic on the replication network interface, particularly on the Group Replication port (default 33061)
Detection Strategies
- Monitor MySQL error logs for repeated GCS-related exceptions, assertion failures, or plugin_group_replication termination messages
- Baseline normal Group Replication message rates and alert on deviations that correlate with node unavailability
- Deploy network IDS signatures that flag anomalous traffic patterns on dedicated replication VLANs
Monitoring Recommendations
- Centralize MySQL error, audit, and performance_schema logs into a SIEM for correlation with network telemetry
- Alert on availability metrics such as Group Replication: member state transitions and primary failover events
- Track process uptime for mysqld across all cluster nodes to detect repeated crash-loop behavior
How to Mitigate CVE-2026-101799
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 any node running an affected 8.0.x, 8.4.x, 9.7.x, or 26.7.x build
- Isolate Group Replication traffic to a dedicated, access-controlled network segment
Patch Information
Oracle released fixes for this vulnerability in the Oracle Critical Patch Update October 2026. Upgrade MySQL Server beyond 8.4.12, 9.7.3, or 26.7.1, and upgrade MySQL Cluster beyond 8.0.49, 8.4.12, 9.7.3, or 26.7.1 according to the branch in use. Validate the patched version with SELECT VERSION(); after upgrade.
Workarounds
- Restrict the Group Replication port (default 33061) to known cluster peers using host firewalls or network ACLs
- Place MySQL replication interfaces on a private, non-shared VLAN inaccessible to untrusted hosts
- Enforce IPsec or similar Layer 3 authentication between cluster nodes to block unauthorized adjacent peers
# Example iptables rule limiting Group Replication port to known cluster peers
iptables -A INPUT -p tcp --dport 33061 -s 10.0.10.11 -j ACCEPT
iptables -A INPUT -p tcp --dport 33061 -s 10.0.10.12 -j ACCEPT
iptables -A INPUT -p tcp --dport 33061 -s 10.0.10.13 -j ACCEPT
iptables -A INPUT -p tcp --dport 33061 -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

