CVE-2026-71073 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 unauthenticated attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. 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 5.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H).
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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 flaw represents a significant availability risk for environments relying on this driver to facilitate database connectivity from ODBC-compliant applications. The core technical issue involves an easily exploitable condition within the connector's processing logic that leads to resource exhaustion or state corruption, resulting in a complete denial of service through application hang or frequent, repeatable crashes. This behavior effectively renders the MySQL Connectors component unusable until it is restarted or the underlying system resources are recovered, disrupting any dependent services and applications relying on database connectivity via this specific driver.
The attack vector for this vulnerability is classified as local with low complexity, requiring no authentication privileges to initiate the exploit sequence against the connector itself. However, a critical prerequisite for successful exploitation is human interaction from an entity other than the attacker. This implies that the vulnerability likely manifests through a user-triggered action within an application utilizing the Connector/ODBC driver, such as opening a specific file type, clicking a malicious link in a web-based interface using ODBC backend connections, or executing a crafted query via a compromised but authenticated client application where social engineering plays a role. The attacker must have logon access to the infrastructure where MySQL Connectors executes, meaning this is not an internet-facing remote code execution flaw but rather a threat targeting internal network segments or trusted hosts within the organization's perimeter.
From a classification perspective, this vulnerability aligns with CWE-400, which covers uncontrolled resource consumption leading to denial of service conditions. The operational impact is strictly limited to availability, as indicated by the CVSS 3.1 base score of 5.5 and the vector string AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. There are no implications for confidentiality or integrity; an attacker cannot read sensitive data nor modify existing records through this specific flaw. The primary consequence is service disruption, which can have cascading effects on business operations that depend on real-time database access. In the context of the MITRE ATT&CK framework, this behavior corresponds to techniques related to Resource Hijacking and Denial of Service, specifically focusing on exhausting system resources or crashing application processes rather than establishing persistence or lateral movement.
Mitigation strategies should prioritize immediate patching to the latest stable version of Oracle MySQL Connectors where this flaw has been addressed by vendor engineering teams. In scenarios where patching is not immediately feasible due to compatibility constraints with legacy applications, organizations should implement network segmentation to restrict access to systems running the vulnerable connector from untrusted or potentially compromised endpoints. Additionally, deploying application whitelisting solutions can help prevent unauthorized ODBC drivers from loading on critical servers. Monitoring for unusual spikes in CPU usage, memory consumption, or frequent process restarts of services utilizing Connector/ODBC can serve as an early detection mechanism for exploitation attempts. Security teams should also review access controls to ensure that only authorized personnel and applications have logon privileges to the infrastructure hosting these connectors, thereby reducing the attack surface available to potential adversaries who might leverage social engineering tactics to trigger the vulnerability.