CVE-2026-60624 in MySQL Connectors
Summary
by MITRE • 07/22/2026
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 9.7.0-9.7.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H).
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 07/22/2026
This vulnerability resides within Oracle MySQL Connectors, specifically in the Connector/J component affecting versions 9.7.0 through 9.7.1. The flaw represents a significant availability risk that can be exploited by unauthenticated attackers with network access across multiple protocols. The vulnerability's accessibility is classified as easily exploitable, meaning that malicious actors can leverage it without requiring specialized skills or prior access to the system. The attack vector requires network connectivity from remote locations, making it particularly concerning for systems exposed to internet-facing environments. The CVSS 3.1 score of 6.5 reflects a high severity level with availability impacts, indicating that successful exploitation can result in complete denial of service conditions that may cause the MySQL Connectors to hang or repeatedly crash.
The technical nature of this vulnerability stems from improper handling of certain network protocols within the Connector/J implementation, creating potential for malicious input processing that leads to system instability. This type of flaw typically manifests through buffer overflows, memory corruption issues, or improper state management during protocol handling. The requirement for human interaction suggests that while the initial exploit may be automated, some form of user involvement is necessary for the attack to succeed, potentially indicating a social engineering component or specific conditions that must be met before the vulnerability can be effectively exploited. The impact severity classification as high availability risk means that successful exploitation results in complete denial of service conditions, where the MySQL Connectors become completely non-functional and require manual intervention to restore normal operations.
The operational implications of this vulnerability extend beyond simple service disruption to potentially compromise entire database infrastructure dependencies. Organizations relying on MySQL Connectors for application connectivity may experience cascading failures throughout their systems, as database connections become unavailable and applications dependent on these connections face complete outages. The repeated crash potential indicates that even a single successful exploitation attempt can cause sustained disruption rather than temporary interruptions, making recovery efforts more complex and time-consuming. This vulnerability affects systems where Connector/J is deployed for client-server communication, potentially impacting web applications, enterprise software, and any system requiring database connectivity through the MySQL protocol stack.
Security mitigations for this vulnerability should prioritize immediate patching of affected versions to 9.7.2 or later releases that contain the necessary security fixes. Network segmentation strategies should be implemented to limit access to MySQL Connectors from untrusted networks, while firewall rules should restrict unnecessary protocol exposure. Organizations should also implement monitoring solutions specifically designed to detect abnormal connection patterns or crash events that may indicate exploitation attempts. Additionally, regular vulnerability assessments and penetration testing should be conducted to identify similar weaknesses in the broader database infrastructure ecosystem. The vulnerability aligns with CWE-121, which addresses stack-based buffer overflow conditions, and maps to ATT&CK technique T1499.004 for network denial of service attacks. Organizations must also consider implementing intrusion detection systems that can identify anomalous behavior patterns associated with this specific vulnerability class and ensure comprehensive backup and recovery procedures are in place to minimize business impact during potential exploitation events.