CVE-2025-30695: 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 5.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% 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:L/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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle Corporation MySQL Server | Affected
| Fixed in– |
AI-suggested
1. Enforce strict network segmentation and firewall rules to limit MySQL Server access only to trusted hosts and networks, reducing exposure to potential attackers. 2. Implement the principle of least privilege rigorously, ensuring that only necessary users have high-level privileges on MySQL Server. Regularly audit and review user privileges to detect and remove unnecessary elevated access. 3. Monitor MySQL Server logs and network traffic for unusual activities such as repeated connection attempts, unexpected data modification queries, or server crashes that could indicate exploitation attempts. 4. Apply defense-in-depth by using database activity monitoring (DAM) tools and intrusion detection systems (IDS) tailored for database environments. 5. Prepare for patch deployment by tracking Oracle’s security advisories closely and testing patches in staging environments to ensure compatibility and stability. 6. Consider temporary compensating controls such as disabling unused network protocols or services that provide access to MySQL Server until patches are available. 7. Educate database administrators and security teams about this vulnerability and the importance of rapid response to suspicious activities. 8. Use multi-factor authentication (MFA) for administrative access to reduce the risk of credential compromise. 9. Backup critical databases regularly and verify backup integrity to enable recovery in case of data corruption or loss due to exploitation.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).