PatchSiren cyber security CVE debrief
CVE-2026-60585 Oracle Corporation CVE debrief
A vulnerability exists in MySQL Server and MySQL Cluster products of Oracle MySQL, specifically in the Server: Replication component. The vulnerability is difficult to exploit and allows high privileged attackers with network access to compromise MySQL Server and MySQL Cluster. Successful attacks can result in takeover of MySQL Server and MySQL Cluster. The affected versions 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. The vulnerability has a CVSS 3.1 Base Score of 6.6, indicating a medium severity. Administrators and users of MySQL Server and MySQL Cluster products should be aware of this vulnerability and take necessary actions to mitigate the risk.
- Vendor
- Oracle Corporation
- Product
- MySQL Server
- CVSS
- MEDIUM 6.6
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-07-28
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-07-28
Who should care
Administrators and users of MySQL Server and MySQL Cluster products should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes applying patches and updates to affected versions, restricting network access, and monitoring and auditing for suspicious activity. Operators, platform administrators, and security teams should review the vulnerability details and assess their exposure.
Technical summary
The vulnerability is located in the Server: Replication component of MySQL Server and MySQL Cluster. The affected versions 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. The vulnerability has a CVSS 3.1 Base Score of 6.6, indicating a medium severity. High privileged attackers with network access can exploit this vulnerability to compromise MySQL Server and MySQL Cluster. The vulnerability allows for takeover of MySQL Server and MySQL Cluster.
Defensive priority
High priority should be given to patching and mitigating this vulnerability, as it can lead to takeover of MySQL Server and MySQL Cluster.
Recommended defensive actions
- Apply patches and updates to affected versions of MySQL Server and MySQL Cluster.
- Restrict network access to MySQL Server and MySQL Cluster.
- Monitor and audit MySQL Server and MySQL Cluster for suspicious activity.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The CVE record was published on 2026-07-21T22:17:58.933Z and was last modified on 2026-07-27T16:18:07.880Z. The NVD entry is currently Undergoing Analysis. This vulnerability affects MySQL Server and MySQL Cluster products of Oracle MySQL, specifically in the Server: Replication component. The evidence provided is limited, and defenders should verify the affected versions and scope. The CVE details are based on the NVD entry and the official CVE record.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-60585 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-60585
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-60585 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-60585
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cpujul2026.html
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.