Skip to main content
VulnerabilityPublished

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

Affects Oracle MySQL ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.9 Medium.

Data as of 21 Nov 2026, 17:34 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 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/mysql-serverOther threatsAffected
  • =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. Immediate mitigation should focus on restricting network access to MySQL Server instances to trusted and authenticated users only, employing strict firewall rules and network segmentation to limit exposure.
  2. Enforce the principle of least privilege rigorously, ensuring that only necessary users have high-privileged access to MySQL servers.
  3. Monitor and audit privileged user activities to detect any anomalous behavior that could indicate exploitation attempts.
  4. Implement resource usage monitoring on MySQL servers to detect unusual spikes or patterns indicative of exploitation attempts targeting the optimizer component.
  5. Since no patches are currently available, consider deploying temporary workarounds such as disabling or limiting features related to the optimizer if feasible and supported by the application workload.
  6. Prepare for rapid patch deployment once Oracle releases an official fix by maintaining an up-to-date asset inventory and patch management process.
  7. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics that can identify attempts to exploit this vulnerability once they become available.
  8. Conduct internal penetration testing and vulnerability assessments focusing on MySQL Server configurations and privilege management to identify and remediate weaknesses proactively.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 9.0.0-9.1.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…