CVE-2025-53054: 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 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% 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 21 Oct 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 |
|---|---|---|
| Oracle Corporation MySQL Server | Affected
| Fixed in– |
AI-suggested
1. Apply official patches from Oracle as soon as they become available to remediate the vulnerability in affected MySQL versions. 2. Restrict network access to MySQL servers by implementing strict firewall rules and network segmentation, allowing only trusted hosts and services to connect. 3. Enforce the principle of least privilege by limiting user and service accounts to only the necessary permissions, reducing the chance of high privilege exploitation. 4. Monitor database logs and network traffic for unusual activities such as unexpected update, insert, or delete commands, or repeated connection attempts that could indicate exploitation attempts. 5. Use intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns. 6. Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools to provide additional layers of defense. 7. Regularly audit and review user privileges and access controls to detect and remediate privilege escalations. 8. Implement robust backup and recovery procedures to restore data integrity in case of unauthorized modifications. 9. Educate administrators and security teams about this vulnerability and ensure incident response plans include scenarios involving database compromise. 10. Avoid exposing MySQL servers directly to the internet; use VPNs or secure tunnels for remote access.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.43, 8.4.0-8.4.6 and 9.0.0-9.4.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).