CVE-2025-50096: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/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 |
|---|---|---|
| Oracle Corporation MySQL Server | Affected
| Fixed in– |
AI-suggested
To mitigate the risk posed by CVE-2025-50096, European organizations should implement the following specific measures: 1) Restrict and tightly control access to infrastructure hosting MySQL Server, ensuring that only authorized personnel have high-privilege logon capabilities. 2) Employ robust privilege management and auditing to detect and prevent unauthorized elevation or misuse of high-privilege accounts. 3) Monitor MySQL Server logs and system resource usage for signs of abnormal activity or resource exhaustion that could indicate exploitation attempts. 4) Segment database servers within the network to limit lateral movement opportunities for attackers who gain initial access elsewhere. 5) Apply defense-in-depth strategies such as host-based intrusion detection systems (HIDS) and endpoint protection to detect and block suspicious activities at the infrastructure level. 6) Stay informed about Oracle's security advisories and promptly apply patches or updates once they become available for this vulnerability. 7) Conduct regular security assessments and penetration testing focusing on privilege escalation and DoS scenarios within the database environment. 8) Implement failover and high-availability configurations for MySQL Server to minimize service disruption in case of a crash or hang. These targeted actions go beyond generic advice by focusing on access control, monitoring, and resilience specific to the nature of this vulnerability.
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 logon to the infrastructure where MySQL Server executes 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).