CVE-2026-21936: Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Cluster.
Affects Oracle MySQL ClusterSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationMySQL Cluster | Affected
| Fixed in– |
| Oracle CorporationMySQL Server | Affected
| Fixed in– |
Oracleoracle/mysql-clusterpkg:rpm/oracle/mysql-clusterOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Apply official Oracle patches as soon as they become available to remediate the vulnerability in affected MySQL Cluster versions. 2. Restrict network access to MySQL Cluster servers, limiting exposure to trusted hosts and protocols only. 3. Enforce strict privilege management by auditing and minimizing high privilege accounts with network access to MySQL servers. 4. Implement network segmentation and firewall rules to isolate database clusters from general network traffic. 5. Monitor MySQL server logs and system behavior for signs of hangs, crashes, or unusual activity indicative of exploitation attempts. 6. Use intrusion detection/prevention systems (IDS/IPS) to detect anomalous protocol usage targeting MySQL services. 7. Regularly review and update incident response plans to include scenarios involving MySQL service disruptions. 8. Conduct security awareness training for administrators to prevent credential compromise and misuse of high privilege accounts. 9. Consider deploying failover and redundancy mechanisms to minimize downtime impact in case of DoS events. 10. Stay informed about vendor advisories and threat intelligence related to MySQL vulnerabilities.
Description
CVE-2026-21936 is a medium severity vulnerability affecting Oracle MySQL Cluster versions 7.6.0, 8.0.0-8.0.44, 8.4.0-8.4.