Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General).

published 2022-01-19 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-26543

cvss: 6.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

Patch / fix

fixed in 1 distros 1

oracle mysql_cluster 7.6.21, 8.0.28

mysql CBL-Mariner 2.0 8.0.28-1

azure linux advisories AZL-7709

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-09-24)

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.3	CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	4.6	AV:N/AC:H/Au:S/C:P/I:P/A:P

Affected products

Oracle Corporation MySQL Cluster

References

oracle.com /security-alerts/cpujan2022.html
vendor-advisory
security.netapp.com /advisory/ntap-20220121-0008/
third-party-advisory
zerodayinitiative.com /advisories/ZDI-22-103/
third-party-advisory

Sources

CVE List CVE-2022-21318
NVD CVE-2022-21318

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Improve version ranges to indicate fix.

Summary