CVE-2025-50096

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

Published: 2025-07-15 Last update: 2025-07-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-50096 is rated Low Risk (20.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.18%). 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-50096

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-06-15 0.10% 0.18% +0.09%
2 2026-05-11 0.01% 0.10% +0.09%
3 2025-07-16 — 0.01% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 3.6 [email protected]

Weakness enumeration for CVE-2025-50096

OS Trackers for CVE-2025-50096

vendor priority summary link
debian not yet assigned CVE-2025-50096 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-50096
redhat medium — https://access.redhat.com/security/cve/CVE-2025-50096
ubuntu medium CVE-2025-50096 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-50096

Affected software / configurations for CVE-2025-50096

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-50096

cvelogic Threat Intelligence