CVE-2025-50081

Vulnerability in the MySQL Client product of Oracle MySQL (component: Client: mysqldump). 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. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Client accessible data as well as unauthorized read access to a subset of MySQL Client accessible data. CVSS 3.1 Base Score 3.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N).

Published: 2025-07-15 Last update: 2025-07-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-50081 is rated Low Risk (28.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.23%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-50081

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-11 0.06% 0.23% +0.17%
2 2026-03-31 0.03% 0.06% +0.03%
3 2025-07-16 0.03%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-50081

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.1 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
0.5 2.5 [email protected]

Weakness enumeration for CVE-2025-50081

OS Trackers for CVE-2025-50081

vendor priority summary link
debian not yet assigned CVE-2025-50081 not yet assigned priority: Debian including 1 source packages (mysql-8.0), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-50081
redhat low https://access.redhat.com/security/cve/CVE-2025-50081
ubuntu medium CVE-2025-50081 medium priority: Ubuntu including 11 source packages (mariadb, mariadb-10.0, …), 64 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 36, not-affected 11, released 7, needs-triage 6, ignored 4. https://ubuntu.com/security/CVE-2025-50081

Affected software / configurations for CVE-2025-50081

Vendor Product Version Raw CPE
oracle mysql >= 8.0.0, <= 8.0.42 cpe:2.3:a:oracle:mysql:*:*:*:*:*:*:*:*
oracle mysql >= 8.4.0, <= 8.4.5 cpe:2.3:a:oracle:mysql:*:*:*:*:*:*:*:*
oracle mysql >= 9.0.0, <= 9.3.0 cpe:2.3:a:oracle:mysql:*:*:*:*:*:*:*:*

References for CVE-2025-50081

cvelogic Threat Intelligence