CVE-2025-50083: Oracle MySQL Server · Uncontrolled Resource Consumption
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 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
To mitigate CVE-2025-50083 effectively, European organizations should: 1) Immediately inventory all MySQL Server instances to identify affected versions (8.0.0-8.0.42, 8.4.0-8.4.5, 9.0.0-9.3.0). 2) Apply vendor patches or updates as soon as Oracle releases them, prioritizing critical production environments. 3) Restrict network access to MySQL servers by implementing strict firewall rules and network segmentation, limiting exposure to trusted hosts and internal networks only. 4) Enforce the principle of least privilege for MySQL user accounts to minimize the risk of exploitation by low-privileged attackers. 5) Monitor MySQL server logs and network traffic for unusual patterns indicative of resource exhaustion or repeated crashes. 6) Implement automated failover and redundancy mechanisms to maintain availability during potential DoS events. 7) Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with signatures tuned to detect anomalous MySQL traffic patterns. 8) Conduct regular security assessments and penetration testing focused on database components to identify and remediate similar vulnerabilities proactively.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). 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 low 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).