Medium severity · published Jul 15, 2025
CVE-2025-50068
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General)
6.7
CVSS
0.2%
EPSS
No
On KEV
Description
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).
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 9% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MC
Mysql Cluster · Oracle
8.0.0 through 8.0.42; 8.4.0 through 8.4.5; 9.0.0 through 9.3.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-50068
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-50068
Patch
https://www.oracle.com/security-alerts/cpujul2025.html
More from Mysql Cluster
9.8
CVE-2021-22931
Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names returned by Domain Name…
8.4
CVE-2026-60163
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Group Replication Plugin)
8.2
CVE-2026-60592
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: NDB Operator)
8.2
CVE-2026-60315
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: X Plugin)
8.2
CVE-2022-21824
Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously…