CVE-2025-50082: Oracle MySQL Server · Easily exploitable vulnerability allows low privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/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
Given the absence of official patches at this time, European organizations should implement several targeted mitigation strategies: 1) Restrict network access to MySQL Server instances by enforcing strict firewall rules and network segmentation, allowing only trusted hosts and applications to communicate with the database server. 2) Employ robust authentication and authorization controls to minimize the privileges of users and services interacting with MySQL, reducing the potential attack surface. 3) Monitor MySQL server logs and network traffic for unusual patterns indicative of repeated connection attempts or resource exhaustion that could signal exploitation attempts. 4) Implement resource limits and timeout configurations within MySQL to mitigate the impact of resource consumption attacks, such as limiting query execution time and connection limits. 5) Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) capable of detecting and blocking anomalous traffic targeting MySQL protocols. 6) Prepare incident response plans focused on rapid detection and recovery from DoS conditions, including automated failover or restart mechanisms to minimize downtime. 7) Stay informed on Oracle’s security advisories for the release of official patches or updates addressing this vulnerability and prioritize timely patching once available. 8) For cloud deployments, leverage provider-specific security controls and managed database services that may already incorporate protections against such vulnerabilities.
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 low 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).