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-101756 Overview
CVE-2026-101756 is a denial of service vulnerability in the Oracle MySQL Server and MySQL Cluster products. The flaw resides in the Server: GIS (Geographic Information System) component. Affected versions include MySQL Server 9.7.0-9.7.3 and 26.7.0-26.7.1, along with MySQL Cluster 9.7.0-9.7.3 and 26.7.0-26.7.1. An authenticated attacker with high privileges and network access can exploit the vulnerability using multiple protocols. Successful exploitation produces a hang or repeatable crash resulting in complete denial of service. The weakness is classified under [CWE-284: Improper Access Control].
Critical Impact
Successful exploitation causes a hang or frequently repeatable crash, delivering complete denial of service against MySQL Server and MySQL Cluster instances.
Affected Products
- Oracle MySQL Server versions 9.7.0 through 9.7.3 and 26.7.0 through 26.7.1
- Oracle MySQL Cluster versions 9.7.0 through 9.7.3 and 26.7.0 through 26.7.1
- Deployments exposing MySQL network protocols to authenticated users
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-101756 published to NVD
- 2026-10-22 - Last updated in NVD database
- October 2026 - Fix included in Oracle Critical Patch Update advisory
Technical Details for CVE-2026-101756
Vulnerability Analysis
The vulnerability affects the GIS subsystem of MySQL Server and MySQL Cluster. GIS handles spatial data types, geometry parsing, and spatial function evaluation. The flaw allows an authenticated high-privileged attacker to send crafted input over MySQL network protocols to trigger a server hang or crash. The condition is repeatable, meaning the attacker can continuously disrupt database availability. Confidentiality and integrity are not impacted. Availability is fully compromised according to the vendor advisory. The EPSS probability for exploitation is 0.422%.
Root Cause
The root cause is improper access control [CWE-284] within the GIS component. Specific internal code paths processing spatial operations do not properly restrict or validate operations initiated by privileged database sessions. When exercised, these code paths lead the server process into an unrecoverable state or trigger a fatal condition that terminates the service.
Attack Vector
The attack vector is network-based. The attacker must already hold high-privilege database credentials and must reach the MySQL instance over one of the supported MySQL protocols. No user interaction is required. The resulting denial of service affects all clients and applications depending on the targeted MySQL Server or MySQL Cluster node. Technical details beyond the vendor summary are not publicly documented. See the Oracle Security Alert October 2026 for the authoritative advisory.
Detection Methods for CVE-2026-101756
Indicators of Compromise
- Unexpected mysqld process crashes or restarts with signal traces referencing GIS or spatial functions
- Repeated client disconnects coinciding with execution of spatial queries by privileged accounts
- Error log entries referencing the GIS subsystem followed by abnormal shutdown
Detection Strategies
- Audit MySQL general and slow query logs for spatial function calls originating from administrative accounts
- Correlate database crash events with authentication logs to identify the originating session
- Enable Oracle MySQL Enterprise Audit to capture statements executed by high-privileged users
Monitoring Recommendations
- Alert on mysqld process termination events and automatic restart loops
- Track login activity for high-privilege MySQL accounts, especially from unexpected network segments
- Monitor availability metrics for MySQL Cluster data nodes to detect repeated hang conditions
How to Mitigate CVE-2026-101756
Immediate Actions Required
- Apply the fixes delivered in the Oracle Critical Patch Update October 2026 to all affected MySQL Server and MySQL Cluster instances
- Inventory MySQL deployments running versions 9.7.0-9.7.3 and 26.7.0-26.7.1 and prioritize upgrades
- Rotate credentials for high-privilege database accounts and review their necessity
Patch Information
Oracle addressed CVE-2026-101756 in the October 2026 Critical Patch Update. Administrators should upgrade to the fixed MySQL Server and MySQL Cluster releases documented in the Oracle advisory. Review the Oracle Security Alert October 2026 for exact fixed version numbers and installation guidance.
Workarounds
- Restrict network access to MySQL instances using firewall rules and bind-address configuration to trusted hosts only
- Limit the number of accounts granted high privileges such as SUPER, PROCESS, or administrative GRANT roles
- Enforce TLS and strong authentication to reduce the risk of credential compromise that could enable exploitation
- Isolate MySQL Cluster management interfaces on dedicated administrative networks
# Example: restrict privileged accounts and tighten network exposure
# Review accounts holding broad privileges
SELECT user, host FROM mysql.user WHERE Super_priv='Y' OR Process_priv='Y';
# Revoke unnecessary high privileges
REVOKE SUPER, PROCESS ON *.* FROM 'app_user'@'%';
# Restrict bind address in my.cnf to internal interface
# [mysqld]
# bind-address = 10.0.0.5
# require_secure_transport = ON
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

