CVE-2025-50102: 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 47% 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 servers by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts and administrative networks only. 2. Enforce the principle of least privilege by auditing and minimizing high-privileged accounts that can access MySQL servers, including service accounts and administrative users. 3. Monitor and log all administrative access and unusual activity on MySQL servers to detect potential misuse of high privileges early. 4. Temporarily disable or restrict less secure protocols or interfaces that provide network access to MySQL if they are not essential. 5. Implement resource limits and timeout settings on MySQL to mitigate the impact of potential resource exhaustion or hanging caused by exploitation attempts. 6. Prepare incident response plans specifically addressing MySQL service availability issues, including rapid failover or service restart procedures. 7. Stay updated with Oracle’s security advisories and apply patches promptly once they become available. 8. Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block suspicious traffic patterns targeting MySQL services. 9. Conduct regular security assessments and penetration testing focusing on database servers to identify privilege escalation and network exposure risks.
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 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).