CVE-2025-50094: 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.5% chance of exploitation in 30 days – higher than 48% 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 |
|---|---|---|
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/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. Restrict network access to MySQL Server to trusted hosts and networks only, employing strict firewall rules and network segmentation to minimize exposure. 2. Enforce the principle of least privilege rigorously, ensuring that only necessary users have high-level privileges on MySQL instances. 3. Monitor and audit privileged user activities to detect any anomalous behavior that could indicate exploitation attempts. 4. Implement robust authentication mechanisms, including multi-factor authentication for administrative access to MySQL. 5. Apply any available patches or updates from Oracle promptly once released. In the absence of patches, consider temporary mitigations such as disabling or restricting vulnerable protocols or interfaces if feasible. 6. Employ resource monitoring and automated alerting to detect unusual resource consumption or service hangs indicative of exploitation. 7. Prepare incident response plans specifically addressing potential DoS scenarios affecting database availability. 8. Regularly review and update network and database security policies to adapt to evolving threat landscapes.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.42, 8.4.5 and 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).