Skip to main content
CVE-2025-50103VulnerabilityPublished Updated

CVE-2025-50103: Oracle MySQL Server · Difficult to exploit 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.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/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-serverpkg:maven/com.oracle/mysql-serverOther threatsAffected
  • =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

European organizations should implement the following specific mitigation strategies: 1) Upgrade MySQL Server to a patched version as soon as Oracle releases a fix for CVE-2025-50103. Until a patch is available, consider temporarily disabling LDAP authentication if feasible, or restrict its use to trusted internal networks only. 2) Enforce strict network segmentation and access controls to limit network exposure of MySQL servers, ensuring that only authorized and trusted hosts can communicate with the database server over the relevant protocols. 3) Implement robust privilege management to minimize the number of accounts with high privileges on MySQL servers, reducing the likelihood of an attacker having the necessary access to exploit this vulnerability. 4) Monitor MySQL server logs and network traffic for unusual patterns indicative of attempts to exploit LDAP authentication or cause resource exhaustion. 5) Employ rate limiting or connection throttling on MySQL server interfaces to mitigate the impact of potential DoS attempts. 6) Conduct regular security audits and penetration testing focused on internal threat vectors, especially for high-privilege accounts and authentication mechanisms. 7) Prepare incident response plans specifically addressing denial-of-service scenarios affecting database availability to ensure rapid recovery and continuity of operations.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: LDAP Auth). Supported versions that are affected are 9.0.0-9.3.0. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

References

Community reviews

Loading reviews…