PatchSiren cyber security CVE debrief
CVE-2026-60182 Oracle Corporation CVE debrief
A vulnerability was discovered in the 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 network access via multiple protocols to compromise MySQL Server and MySQL Cluster. Successful attacks can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server and MySQL Cluster. The vulnerability has a CVSS 3.1 Base Score of 4.4 (Availability impacts) and a CVSS Vector of (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).
- Vendor
- Oracle Corporation
- Product
- MySQL Server
- CVSS
- MEDIUM 4.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-07-27
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-07-27
Who should care
Administrators and users of MySQL Server and MySQL Cluster products, especially those with high privileges, should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes reviewing and applying patches, restricting network access, and monitoring for unusual activity. Additionally, security teams and vulnerability management teams should prioritize this vulnerability based on its potential impact on the organization's assets and data.
Technical summary
The vulnerability has a CVSS 3.1 Base Score of 4.4 (Availability impacts) and a CVSS Vector of (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H). It is caused by a weakness in the Server: Clone Plugin component of MySQL Server and MySQL Cluster. The vulnerability allows a high-privileged attacker with network access via multiple protocols to compromise MySQL Server and MySQL Cluster, potentially leading to a complete DOS. 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.
Defensive priority
Medium priority should be given to patching or mitigating this vulnerability, as it can lead to a complete DOS of MySQL Server and MySQL Cluster.
Recommended defensive actions
- Apply the patches provided by Oracle to affected versions of MySQL Server and MySQL Cluster.
- Restrict network access to MySQL Server and MySQL Cluster to only necessary personnel.
- Monitor MySQL Server and MySQL Cluster for unusual activity or crashes.
- Consider implementing compensating controls, such as intrusion detection and prevention systems.
- Review and update asset inventory to identify potentially affected systems.
- Perform exposure review to determine the potential impact on the organization.
- Track exceptions and retest remediated assets to ensure the vulnerability is properly mitigated.
Evidence notes
The CVE record was published on 2026-07-21T22:17:19.183Z and was last modified on 2026-07-27T14:47:50.577Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus and may not reflect the full scope of the vulnerability. Defenders should verify the affected versions and configurations to assess their exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-60182 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-60182
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-60182 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-60182
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.