CVE-2025-53053: Oracle MySQL Server · Uncontrolled Resource Consumption
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 08:30 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle.mysql/mysql-serverpkg:maven/com.oracle.mysql/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
European organizations should implement the following specific mitigations: 1) Monitor Oracle's security advisories closely and apply patches promptly once they become available for the affected MySQL versions. 2) Restrict network access to MySQL servers by enforcing strict firewall rules and network segmentation to limit exposure to trusted hosts and services only. 3) Enforce the principle of least privilege by ensuring that only necessary users have high privilege access to MySQL servers, and regularly audit privilege assignments. 4) Implement robust authentication mechanisms and consider multi-factor authentication for administrative access to reduce the risk of credential compromise. 5) Employ database activity monitoring and anomaly detection to identify unusual DML operations or service disruptions indicative of exploitation attempts. 6) Regularly back up databases and test restoration procedures to minimize data loss impact in case of unauthorized modifications or service outages. 7) Harden MySQL configurations by disabling unused protocols and services to reduce the attack surface. 8) Conduct internal penetration testing and vulnerability assessments focusing on privilege escalation and network access controls to identify potential weaknesses before exploitation.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). 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).