CVE-2025-30722: Oracle MySQL Cluster · Difficult to exploit vulnerability allows low privileged attacker with network access via multiple
Affects Oracle MySQL ClusterSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation 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 |
|---|---|---|
Mysqlmysql/mysql-clientpkg:deb/mysql/mysql-clientOther 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 patches or updates from Oracle as soon as they become available for the affected MySQL Cluster versions. 2. Restrict network access to MySQL Cluster clients by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts and networks only. 3. Use encrypted connections (e.g., TLS) for MySQL Cluster communications to reduce the risk of interception or man-in-the-middle attacks. 4. Monitor database logs and network traffic for unusual access patterns or unauthorized data modification attempts, employing anomaly detection tools where possible. 5. Implement least privilege principles for database users and service accounts interacting with MySQL Cluster to minimize potential damage from compromised clients. 6. Regularly audit MySQL Cluster configurations and client deployments to ensure they do not expose unnecessary network services or protocols. 7. Educate database administrators and security teams about this vulnerability and encourage proactive incident response planning. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts targeting MySQL Cluster protocols.
Description
Vulnerability in the MySQL Client product of Oracle MySQL (component: Client: mysqldump). 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. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Client accessible data as well as unauthorized update, insert or delete access to some of MySQL Client accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N).