CVE-2025-50087

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 creation, deletion or modification access to critical data or all MySQL Server accessible data. CVSS 3.1 Base Score 4.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N).

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

CVE-2025-50087 is rated Moderate Risk (40.2/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.36%). Review affected assets and schedule remediation.

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

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.09% 0.36% +0.27%
2 2026-03-31 0.05% 0.09% +0.04%
3 2026-03-20 — 0.05% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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: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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 3.6 [email protected]

Weakness enumeration for CVE-2025-50087

OS Trackers for CVE-2025-50087

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

Affected software / configurations for CVE-2025-50087

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

cvelogic Threat Intelligence