Skip to main content
CVE-2025-50079VulnerabilityPublished

CVE-2025-50079: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with network access via multiple

Affects Oracle MySQL ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle.mysql/mysql-serverpkg:maven/com.oracle.mysql/mysql-serverOther threatsAffected
  • =8.0.0
  • =8.4.0
  • =9.0.0
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: 1) Immediately audit and restrict high-privileged access to MySQL servers, ensuring that only authorized personnel have such privileges and that network access is tightly controlled. 2) Implement network segmentation and firewall rules to limit exposure of MySQL servers to trusted internal networks only, reducing the attack surface. 3) Monitor MySQL server logs and performance metrics for unusual activity or signs of resource exhaustion that could indicate exploitation attempts. 4) Apply principle of least privilege to database users and services to minimize the number of accounts with high privileges. 5) Prepare incident response plans specifically addressing MySQL service outages to reduce downtime impact. 6) Stay alert for official patches or updates from Oracle and plan for timely deployment once available. 7) Consider deploying database high-availability solutions or failover mechanisms to maintain service continuity in case of DoS events. 8) Conduct regular security training for database administrators to recognize and prevent misuse of privileged access.

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).

References

Community reviews

Loading reviews…