PatchSiren cyber security CVE debrief
CVE-2026-47064 Oracle Corporation CVE debrief
A vulnerability was discovered in the MySQL Server and MySQL Cluster products of Oracle MySQL, specifically in the Server: Optimizer 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 vulnerability allows a low-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.
- Vendor
- Oracle Corporation
- Product
- MySQL Server
- CVSS
- MEDIUM 6.5
- 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
System administrators and security teams responsible for MySQL Server and MySQL Cluster installations, particularly those using affected versions, should be aware of this vulnerability and take necessary actions to mitigate the risk.
Technical summary
The vulnerability has a CVSS 3.1 Base Score of 6.5, indicating a medium severity level. The CVSS Vector is (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), showing that the vulnerability allows attackers to impact availability (A) but not confidentiality (C) or integrity (I). The vulnerability is categorized under CWE-284. This vulnerability affects MySQL Server versions 8.4.0-8.4.10 and 9.7.0-9.7.1, as well as MySQL Cluster versions 8.0.0-8.0.47, 8.4.0-8.4.10, and 9.7.0-9.7.1. A low-privileged attacker with network access via multiple protocols can exploit this vulnerability to compromise MySQL Server and MySQL Cluster, potentially causing a hang or frequently repeatable crash (complete DOS).
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 patches or updates provided by Oracle to affected MySQL Server and MySQL Cluster installations.
- 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 Web Application Firewalls (WAFs), to detect and prevent exploitation attempts.
- Review and update asset inventory to ensure all affected systems are accounted for.
- Perform regular security audits to identify potential vulnerabilities.
- Establish a change management process to ensure timely application of security patches.
Evidence notes
The CVE record was published on 2026-07-21T22:17:12.383Z and was last modified on 2026-07-27T14:52:01.920Z. The NVD entry is currently Analyzed. The evidence is based on the official CVE record and NVD detail page. The affected versions and products are confirmed based on the CVE and NVD information. The CVSS score and vector are also confirmed based on the CVE record.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-47064 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-47064
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-47064 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47064
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.