CVE-2025-30696: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 59% 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 15 Apr 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-25.
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. Immediately review and restrict high privilege accounts on MySQL servers to the minimum necessary, ensuring that only trusted administrators have such access. 2. Implement strict network segmentation and firewall rules to limit network access to MySQL servers only to authorized hosts and management networks. 3. Monitor MySQL server logs and network traffic for unusual activity or repeated connection attempts that could indicate exploitation attempts. 4. Apply any available patches or updates from Oracle as soon as they are released for the affected MySQL versions. 5. Consider upgrading to newer MySQL versions beyond 9.2.0 if they are confirmed not vulnerable. 6. Use intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns. 7. Employ database activity monitoring solutions to detect abnormal commands or crashes. 8. Regularly back up MySQL databases to enable rapid recovery in case of service disruption. 9. Conduct internal audits of privilege assignments and network configurations to ensure compliance with least privilege and zero trust principles. 10. Educate administrators about the vulnerability and the importance of safeguarding privileged credentials.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: PS). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.0. Easily exploitable 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.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).