PatchSiren cyber security CVE debrief
CVE-2026-60183 Oracle Corporation CVE debrief
A vulnerability exists in MySQL Server and MySQL Cluster products of Oracle MySQL, specifically in the Server: Clone Plugin component. 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. This difficult-to-exploit vulnerability allows a high-privileged attacker with logon to the infrastructure where MySQL Server and MySQL Cluster execute to compromise these products. Successful attacks can result in the takeover of MySQL Server and MySQL Cluster. The vulnerability has a CVSS 3.1 Base Score of 6.4, indicating a medium severity level.
- Vendor
- Oracle Corporation
- Product
- MySQL Server
- CVSS
- MEDIUM 6.4
- 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 versions 8.4.0-8.4.10, 9.7.0-9.7.1, and 8.0.0-8.0.47 should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes reviewing and applying patches, restricting access, and monitoring for suspicious activity. Vulnerability management and security teams should prioritize patching and consider compensating controls for exposed systems.
Technical summary
The vulnerability, CVE-2026-60183, has a CVSS 3.1 Base Score of 6.4, indicating a medium severity level. The CVSS Vector is (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H), showing that the vulnerability allows for high confidentiality, integrity, and availability impacts. The vulnerability is caused by a weakness in the Server: Clone Plugin component of MySQL Server and MySQL Cluster. Successful attacks can result in the takeover of MySQL Server and MySQL Cluster. Administrators should focus on patching or mitigating this vulnerability, especially in environments where high-privileged access is common.
Defensive priority
High priority should be given to patching or mitigating this vulnerability, especially in environments where high-privileged access is common. Defenders should focus on verifying affected systems, restricting access, and monitoring for suspicious activity.
Recommended defensive actions
- Apply the patches provided by Oracle for MySQL Server and MySQL Cluster.
- Restrict access to the infrastructure where MySQL Server and MySQL Cluster execute.
- Monitor for any suspicious activity related to the Server: Clone Plugin component.
- Consider implementing compensating controls, such as additional authentication or authorization mechanisms.
- Review and update asset inventory to identify exposed systems.
- Plan and track remediation through normal change control.
- Verify and document exceptions and retest remediated assets.
Evidence notes
The CVE record was published on 2026-07-21T22:17:19.290Z and was last modified on 2026-07-27T14:46:12.960Z. The NVD entry is currently Analyzed. Evidence is limited to CVE and NVD information. Defenders should verify MySQL Server and MySQL Cluster versions, review official advisories, and monitor for suspicious activity related to the Server: Clone Plugin component.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-60183 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-60183
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-60183 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-60183
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cpujul2026.html
[email protected] - Vendor Advisory
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.