CVE-2025-50093: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- 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: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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mysqlmysql/mysql-serverpkg:deb/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
1. Immediate mitigation should focus on restricting network access to MySQL Server instances to trusted and necessary hosts only, using network segmentation and firewall rules to limit exposure. 2. Enforce strict access controls and privilege management to ensure that only authorized users have high-level privileges on MySQL servers. 3. Monitor MySQL server logs and network traffic for unusual activity that could indicate attempts to exploit this vulnerability, such as repeated connection attempts or abnormal query patterns. 4. Implement resource usage monitoring and automated alerts to detect early signs of resource exhaustion or server hangs. 5. Prepare incident response plans specifically for MySQL service disruptions, including rapid failover or restart procedures to minimize downtime. 6. Stay updated with Oracle's security advisories for the release of patches or workarounds and prioritize timely application of any available fixes. 7. Consider deploying MySQL servers in high-availability configurations to reduce the impact of potential DoS conditions. 8. Conduct regular security audits and penetration testing focusing on privilege escalation and network access controls to prevent attackers from gaining the required high privileges.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). 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).