CVE-2026-61144 in MySQL Server MySQL Cluster
Summary
by MITRE • 07/22/2026
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are MySQL Server: 9.7.0-9.7.1; MySQL Cluster: 9.7.0-9.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 07/22/2026
This vulnerability resides within the server optimizer component of MySQL Server and MySQL Cluster versions 9.7.0 through 9.7.1, representing a significant availability risk that can be exploited by attackers with high privileges and network access. The flaw manifests as a condition that allows for complete denial of service through either hanging or repeated crashes of the database systems, fundamentally undermining their operational integrity. This vulnerability type aligns with CWE-476 which describes null pointer dereference conditions, though the specific impact here involves system instability rather than direct memory corruption. The CVSS 3.1 scoring of 4.9 reflects the high availability impact and the relatively low attack complexity requirements, indicating that a determined adversary with elevated privileges can reliably disrupt services.
The technical nature of this vulnerability suggests an issue within the query optimization logic where malformed or specially crafted queries might trigger unexpected behavior in the server's execution engine. Attackers with administrative or high-privilege access levels can leverage this weakness to send malicious inputs that cause the optimizer to enter a state where it either becomes unresponsive or repeatedly crashes, effectively rendering the database service unavailable to legitimate users and applications. The vulnerability's exploitability rating of easily exploitable indicates that the attack vector requires minimal sophistication once the attacker has achieved sufficient privileges within the network environment.
From an operational perspective, this vulnerability presents substantial risk to organizations relying on MySQL Server and Cluster for critical business operations, as the complete denial of service can result in extended downtime and potential data access interruptions. The impact extends beyond simple service disruption since database unavailability can cascade through dependent applications and services that rely on consistent database connectivity for their operation. Organizations using these specific versions should consider the vulnerability's potential for causing widespread operational disruption, particularly in environments where database availability is mission-critical for business continuity.
Mitigation strategies should focus on immediate version upgrades to patched releases of MySQL Server and Cluster, as Oracle typically addresses such availability vulnerabilities through security patches. Network segmentation and access controls should be reinforced to limit privileged access points and reduce the attack surface available to potential adversaries. Additionally, implementing monitoring solutions that can detect unusual system behavior or repeated crash patterns may help identify exploitation attempts before they cause significant disruption. The vulnerability's classification under the ATT&CK framework would likely map to privilege escalation and denial of service tactics, emphasizing the need for layered defensive measures that address both access control and system resilience requirements. Organizations should also consider implementing database activity monitoring and anomaly detection systems to identify potentially malicious query patterns that could trigger this specific optimizer flaw.