CVE-2026-60585 in MySQL Server
Summary
by MITRE • 07/22/2026
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are MySQL Server: 8.4.0-8.4.10, 9.7.0-9.7.1; MySQL Cluster: 8.0.0-8.0.47, 8.4.0-8.4.10 and 9.7.0-9.7.1. Difficult to exploit 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 takeover of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H).
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 07/22/2026
This vulnerability resides within the replication component of MySQL Server and MySQL Cluster systems, representing a significant security weakness that affects multiple version ranges including MySQL Server 8.4.0-8.4.10 and 9.7.0-9.7.1, alongside MySQL Cluster versions 8.0.0-8.0.47, 8.4.0-8.4.10, and 9.7.0-9.7.1. The flaw operates at a critical level within the database infrastructure, specifically targeting the replication mechanisms that facilitate data synchronization between primary and secondary servers. According to CVSS 3.1 scoring methodology with a base score of 6.6, this vulnerability presents a high impact threat with confidentiality, integrity, and availability implications, as indicated by the vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H.
The technical nature of this vulnerability allows for privilege escalation attacks where an attacker with network access can exploit the replication functionality to gain unauthorized control over database servers. The difficulty level of exploitation is classified as high, requiring both network connectivity and elevated privileges, typically corresponding to administrative or high-privilege user accounts within the database environment. This characteristic aligns with CWE-284 (Improper Access Control) and reflects attack patterns consistent with those documented in the MITRE ATT&CK framework under privilege escalation techniques, particularly targeting database server components. The replication mechanism itself becomes a vector for unauthorized access where legitimate administrative operations can be subverted by malicious actors.
The operational impact of successful exploitation can result in complete compromise of MySQL Server and Cluster environments, potentially allowing attackers to execute arbitrary code, modify or delete database contents, and disrupt service availability. This level of compromise directly affects the fundamental security tenets of database systems, enabling unauthorized access to sensitive data while undermining the integrity of the entire replication topology. The vulnerability's potential for system takeover means that organizations relying on MySQL replication for data consistency and disaster recovery may face complete service interruption and data loss scenarios. Organizations using these affected versions must recognize that their backup and recovery mechanisms could be compromised, as replication is often used for creating secondary database instances.
Mitigation strategies should prioritize immediate patching of affected systems with the latest Oracle MySQL updates addressing this specific vulnerability. Network segmentation and access control measures provide additional defense layers by limiting direct network access to database servers and implementing strict firewall rules. Monitoring for unusual replication activity or unauthorized administrative connections can help detect exploitation attempts before full compromise occurs. Security teams should implement principle of least privilege for database accounts, ensuring that replication users have only necessary permissions rather than administrative privileges. Regular vulnerability assessments and penetration testing focused on database replication components can identify additional weaknesses in the overall database security posture, while also supporting compliance requirements under standards such as pci dss and iso 27001 that mandate protection of sensitive data through robust access controls and monitoring mechanisms.