Skip to main content
CVE-2025-50092VulnerabilityPublished

CVE-2025-50092: Oracle MySQL Server · Uncontrolled Resource Consumption

Affects Oracle MySQL ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% 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. 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. Restrict network access to MySQL Server instances strictly to trusted and necessary users and systems, minimizing exposure to high-privileged accounts over the network. 2. Implement network segmentation and firewall rules to limit access to MySQL ports from untrusted networks. 3. Monitor MySQL Server logs and system performance metrics for signs of hangs or crashes that could indicate exploitation attempts. 4. Apply the principle of least privilege to MySQL user accounts, ensuring that high-privileged network access is granted only when absolutely necessary. 5. Prepare incident response plans specifically for MySQL service disruptions, including automated failover or restart procedures to minimize downtime. 6. Stay alert for official patches or updates from Oracle and plan rapid deployment once available. 7. Consider deploying MySQL in high-availability configurations to mitigate the impact of potential DoS conditions. 8. Conduct regular vulnerability assessments and penetration testing focusing on database services to detect and remediate exposure to this and similar vulnerabilities.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.42, 8.4.0-8.4.5 and 9.0.0-9.3.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…