CVE-2026-71079 in MySQL Connectors
Summary
by MITRE • 08/19/2026
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/ODBC). The supported version that is affected is 26.7.0. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Connectors. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/19/2026
The identified vulnerability resides within the Connector/ODBC component of Oracle MySQL Connectors, specifically affecting version 26.7.0 and potentially other supported releases in that lineage. This software serves as a critical bridge allowing applications to interact with MySQL databases using the Open Database Connectivity standard. The flaw is characterized by its susceptibility to exploitation by attackers who possess low-level privileges but have network access through multiple protocols. This accessibility vector significantly broadens the attack surface, as it does not require complex authentication bypasses or physical proximity, relying instead on standard network connectivity and basic user credentials within the database environment.
The technical nature of this flaw centers on a resource management error that leads to system instability under specific conditions. When an attacker sends crafted requests through the ODBC interface, the connector fails to properly handle certain inputs or states, leading to excessive resource consumption or logic errors that trigger a hang condition. This results in a complete denial of service where the MySQL Connector process becomes unresponsive and frequently crashes. The impact is strictly confined to availability, as there are no indications of data exfiltration, integrity modification, or unauthorized privilege escalation associated with this specific exploit path. Consequently, while the database server itself may remain operational depending on its architecture, any application relying on this specific connector instance will lose connectivity, effectively halting business processes that depend on real-time data access through ODBC.
From a classification perspective, this vulnerability aligns with CWE-400, which describes uncontrolled resource consumption leading to denial of service conditions. The ability for an attacker to trigger these crashes repeatedly indicates a lack of robust input validation and state management within the connector's handling of network packets or query structures. In terms of offensive security frameworks, this behavior maps closely to MITRE ATT&CK technique T1499, Endpoint Denial of Service, specifically under methods that involve resource exhaustion via application layer attacks. The low attack complexity and lack of user interaction requirements further classify it as a straightforward exploitation scenario for any actor with network access and valid database credentials.
The operational impact of this vulnerability is severe due to the critical role ODBC connectors play in enterprise data integration pipelines. Applications ranging from legacy business intelligence tools to modern web backends may rely on these connections for routine operations. A successful exploit disrupts service availability, leading to downtime, lost productivity, and potential revenue loss depending on the duration of the outage. Since the vulnerability allows for repeatable crashes, an attacker can sustain a denial-of-service condition indefinitely by continuously sending malicious payloads until the connector is restarted or replaced. This persistence makes it particularly dangerous in environments where high availability is mandated but automated failover mechanisms are not fully configured to handle sudden process terminations gracefully.
Mitigation strategies must focus on immediate patching and network segmentation. Oracle has likely released updated versions of MySQL Connectors that address this resource handling flaw; therefore, upgrading to the latest stable release of Connector/ODBC is the primary remediation step. Organizations should verify their current version against vendor advisories and apply patches during scheduled maintenance windows. In addition to software updates, implementing network access controls can reduce exposure. Restricting ODBC connection ports to only those IP addresses or subnets that require database connectivity limits the pool of potential attackers who can attempt exploitation. Furthermore, deploying intrusion detection systems capable of identifying anomalous query patterns or excessive connection attempts from single sources may help mitigate ongoing attacks while patching is underway. Regular auditing of connector configurations and ensuring that low-privileged accounts do not have unnecessary network access to critical data services are also essential defensive measures to minimize the risk profile associated with this vulnerability.