CVE-2025-21519: Oracle MySQL Server · Difficult to exploit vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Jan 2025
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 |
|---|---|---|
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/mysql-serverOther 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 Oracle's official patches immediately once released to address CVE-2025-21519. 2. Restrict network access to MySQL servers using firewalls and network segmentation, allowing only trusted administrative hosts. 3. Enforce the principle of least privilege for MySQL user accounts, ensuring high privilege accounts are limited and monitored. 4. Implement robust authentication and authorization controls to prevent unauthorized privilege escalation. 5. Monitor MySQL server logs and system behavior for signs of hangs, crashes, or unusual activity indicative of exploitation attempts. 6. Conduct regular security audits and vulnerability assessments on MySQL deployments. 7. Consider deploying failover and redundancy mechanisms to minimize service disruption in case of DoS. 8. Educate administrators about the risks of exposing MySQL services directly to untrusted networks. 9. Use network intrusion detection systems (NIDS) to detect anomalous traffic patterns targeting MySQL protocols. 10. Maintain an incident response plan that includes procedures for database service outages.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.40 and prior, 8.4.3 and prior and 9.1.0 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).