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-101772 Overview
CVE-2026-101772 is a high-severity vulnerability in the Client programs component of Oracle MySQL Server and MySQL Cluster. The flaw allows an unauthenticated attacker with network access via multiple protocols to compromise affected database instances. Successful exploitation results in full takeover of the targeted MySQL Server or MySQL Cluster deployment. Oracle addressed the issue in the October 2026 Critical Patch Update. The weakness maps to [CWE-284: Improper Access Control].
Critical Impact
Unauthenticated network attackers can achieve full takeover of MySQL Server and MySQL Cluster instances, impacting confidentiality, integrity, and availability.
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, 9.7.0–9.7.3, and 26.7.0–26.7.1
- Oracle MySQL Client programs bundled with the affected server releases
Discovery Timeline
- 2026-10-20 - CVE-2026-101772 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-101772
Vulnerability Analysis
The vulnerability resides in the Client programs component shipped with Oracle MySQL Server and MySQL Cluster. An attacker can reach the vulnerable code path over the network using multiple protocols without providing credentials. Oracle categorizes the issue as difficult to exploit, meaning the attacker must satisfy specific preconditions beyond their direct control. When exploitation succeeds, the attacker gains full control over the database service, including the ability to read, modify, and destroy data. The scope remains unchanged, so impact is contained to the vulnerable MySQL component, but that component typically holds high-value structured data.
Root Cause
The flaw is classified as improper access control [CWE-284] within MySQL client-side handling. The affected client logic fails to adequately restrict operations that should require authentication or trusted context, allowing a remote, unauthenticated actor to influence server behavior through client-protocol interactions.
Attack Vector
Exploitation occurs over the network and does not require user interaction or prior privileges. Oracle notes that multiple protocols can be used to reach the vulnerable surface, broadening exposure in environments where MySQL Server or Cluster services are directly or indirectly reachable. Because full takeover is possible, successful exploitation grants administrative control over the database instance. No public proof-of-concept code or in-the-wild exploitation has been reported at the time of publication, and the CVE is not listed in the CISA Known Exploited Vulnerabilities catalog. See the Oracle Critical Patch Update October 2026 for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-101772
Indicators of Compromise
- Unexpected administrative queries, new privileged accounts, or GRANT statements executed against MySQL Server or MySQL Cluster nodes
- Anomalous outbound connections or data egress from database hosts to untrusted networks
- MySQL error log entries referencing unexpected client protocol negotiations or malformed handshakes
Detection Strategies
- Inventory MySQL Server and MySQL Cluster instances and compare installed versions against the vulnerable ranges listed by Oracle
- Monitor MySQL general_log and audit_log for authentication anomalies, unexpected root-level activity, and schema modifications
- Alert on new or changed MySQL user accounts, privilege grants, and plugin installations that could indicate post-exploitation persistence
Monitoring Recommendations
- Centralize MySQL audit and error logs into a SIEM or data lake for behavioral correlation and long-term retention
- Baseline normal client traffic to MySQL ports (3306, 33060, Cluster management ports) and flag deviations such as unknown source IPs or unusual protocol mixes
- Track process creation and outbound network behavior on database hosts to identify command execution following database compromise
How to Mitigate CVE-2026-101772
Immediate Actions Required
- Apply the Oracle October 2026 Critical Patch Update to all MySQL Server and MySQL Cluster deployments in the affected version ranges
- Restrict network reachability of MySQL services to trusted application tiers using firewalls, security groups, and network segmentation
- Audit MySQL user accounts, privileges, and recent configuration changes for signs of unauthorized modification
Patch Information
Oracle released fixes for CVE-2026-101772 in the Oracle Critical Patch Update October 2026. Upgrade MySQL Server past 8.4.12, 9.7.3, or 26.7.1 as applicable, and upgrade MySQL Cluster past 8.0.49, 8.4.12, 9.7.3, or 26.7.1. Review the advisory for exact fixed-release numbers and backport guidance.
Workarounds
- Block MySQL protocol ports at the perimeter and limit access to allow-listed application hosts and administrative jump boxes
- Enforce TLS for all client-server MySQL connections and disable unused network protocols on the database tier
- Run MySQL services with least-privilege operating system accounts and isolate database hosts in dedicated network segments
# Example: restrict MySQL network exposure using firewalld until patches are applied
sudo firewall-cmd --permanent --zone=public --remove-service=mysql
sudo firewall-cmd --permanent --zone=internal --add-rich-rule='rule family="ipv4" source address="10.0.10.0/24" port protocol="tcp" port="3306" accept'
sudo firewall-cmd --reload
# Verify current MySQL Server version against Oracle's fixed releases
mysql -V
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

