CVE-2026-83404 in MySQL Connectors
Summary
by MITRE • 10/21/2026
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/Python). The supported version that is affected is 26.7.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Connectors accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/21/2026
The identified vulnerability resides within the Connector/Python component of Oracle MySQL Connectors, specifically affecting version 26.7.0 and potentially earlier versions depending on the specific patch status. This security flaw represents a significant risk to database integrity and confidentiality because it allows for unauthorized access without requiring any form of authentication from the attacker. The nature of this vulnerability is particularly concerning given that Connector/Python serves as a critical bridge between Python applications and MySQL databases, meaning that any compromise in this layer can expose sensitive data stored within the backend systems.
From a technical perspective, the flaw enables an unauthenticated actor to exploit weaknesses through multiple network protocols. This broad attack surface implies that the vulnerability is not limited to a single communication channel but can be triggered via various standard database interaction methods supported by the connector. The ease of exploitation suggests that the underlying code lacks sufficient input validation or access control checks before processing requests from remote clients. Consequently, an attacker with basic networking capabilities and no prior credentials can interact directly with the MySQL server through this compromised component to extract data.
The operational impact of successfully exploiting this vulnerability is severe, primarily centered around a high-impact confidentiality breach. As indicated by the CVSS 3.1 base score of 7.5, which classifies it as High severity, the primary consequence is unauthorized access to critical data and potentially complete access to all MySQL Connectors accessible data. This means that sensitive information such as user credentials, financial records, personal identifiable information, or proprietary business logic could be exfiltrated by malicious actors. While integrity and availability impacts are listed as none in this specific vector, the loss of confidentiality alone is sufficient to cause significant regulatory, legal, and reputational damage to organizations relying on these connectors for their application infrastructure.
In terms of industry standard classifications, this vulnerability aligns with CWE-287 Improper Authentication, where an actor fails to adequately prove its identity before being granted access. Furthermore, the exploitation method maps closely to MITRE ATT&CK techniques related to Initial Access and Credential Access, specifically involving network-based attacks against database services. The ability to bypass authentication mechanisms entirely places this flaw in a category of critical importance for security audits focusing on external-facing or internal service-to-service communication paths that utilize MySQL connectors.
To mitigate the risks associated with this vulnerability, immediate action is required to update Oracle MySQL Connectors to a patched version where the specific code path leading to unauthorized access has been secured. Organizations should also implement network-level controls such as firewalls and intrusion detection systems to restrict direct database port access to only trusted application servers. Additionally, adopting principles of least privilege for database accounts used by applications can limit the scope of damage even if an exploit is attempted. Regular vulnerability scanning and patch management cycles are essential to ensure that connector libraries remain up-to-date against known exploits in this component family.