Skip to main content
VulnerabilityPublished

CVE-2025-53069: Oracle MySQL Server · Unthrottled Resource Allocation

Affects Oracle MySQL ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/mysql-serverOther threatsAffected
  • =8.0.0
  • =8.4.0
  • =9.0.0
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. Monitor Oracle's official channels closely for patches addressing CVE-2025-53069 and apply them promptly once released.
  2. Restrict network access to MySQL servers using firewalls and network segmentation to limit exposure to trusted hosts and administrators only.
  3. Enforce strict access controls and audit administrative privileges to reduce the risk of high privileged account compromise.
  4. Implement robust monitoring and alerting for MySQL server availability and unusual crash or hang patterns to detect exploitation attempts early.
  5. Consider deploying MySQL in high availability configurations with failover capabilities to minimize downtime impact.
  6. Review and harden MySQL configuration to disable unused protocols and services that could be leveraged for exploitation.
  7. Conduct regular security assessments and penetration testing focusing on privilege escalation and denial of service scenarios.
  8. Educate system administrators about this vulnerability and the importance of privilege management and network controls.
  9. Use intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns.
  10. Prepare incident response plans specifically addressing database service outages caused by denial of service attacks.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Components Services). 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. 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).

References

Community reviews

Loading reviews…