CVE-2025-50078: 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 |
|---|---|---|
| Oracle Corporation MySQL Server | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-50078 effectively, European organizations should: 1) Prioritize upgrading MySQL Server to patched versions as soon as Oracle releases them, monitoring Oracle's advisories closely. 2) Implement network-level controls to restrict access to MySQL Server ports (default 3306) to trusted hosts and networks only, using firewalls and network segmentation to minimize exposure. 3) Employ intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous traffic patterns indicative of DoS attempts targeting MySQL. 4) Enforce strict access controls and monitor for unusual low-privilege network activity that could indicate exploitation attempts. 5) Utilize connection throttling and query rate limiting where supported to reduce the risk of resource exhaustion. 6) Maintain robust backup and recovery procedures to minimize downtime in case of service disruption. 7) Conduct regular vulnerability assessments and penetration testing focusing on database services to identify potential exploitation paths. 8) Consider deploying MySQL in high-availability configurations with failover capabilities to reduce single points of failure. These measures go beyond generic advice by focusing on network access restrictions, proactive monitoring, and architectural resilience tailored to this specific vulnerability.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). 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).