CVE-2025-50068

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). 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 Cluster executes to compromise MySQL Cluster. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

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

CVE-2025-50068 is rated Moderate Risk (41.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). 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-50068

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.19% +0.14%
2 2026-04-10 0.01% 0.06% +0.04%
3 2025-07-16 — 0.01% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]

Weakness enumeration for CVE-2025-50068

OS Trackers for CVE-2025-50068

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2025-50068

Affected software / configurations for CVE-2025-50068

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

References for CVE-2025-50068

cvelogic Threat Intelligence