CVE-2025-50099: 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/mysqlpkg:maven/com.oracle/mysqlOther 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 this vulnerability, European organizations should prioritize the following actions: 1) Monitor Oracle's official channels for patches or updates addressing CVE-2025-50099 and apply them promptly once available. 2) Restrict network access to MySQL Server instances to trusted hosts and networks only, employing network segmentation and firewall rules to limit exposure. 3) Enforce strict access controls and privilege management to minimize the number of users with high privileges on MySQL Servers, including regular audits of administrative accounts and roles. 4) Implement robust monitoring and alerting for unusual MySQL Server behavior, such as frequent crashes or hangs, to enable rapid detection and response. 5) Consider deploying rate limiting or connection throttling mechanisms to reduce the risk of resource exhaustion attacks. 6) Conduct regular backups and ensure disaster recovery plans are tested to minimize downtime impact. 7) Harden MySQL Server configurations by disabling unnecessary protocols or services that could be exploited. These measures go beyond generic advice by focusing on reducing the attack surface, limiting privilege escalation opportunities, and enhancing operational resilience.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). 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).