CVE-2023-21860 [Medium] | Security Vulnerability in Mysql Cluster

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: Internal Operations). Supported versions that are affected are 7.4.38 and prior, 7.5.28 and prior, 7.6.24 and prior and 8.0.31 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the 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:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-30	0.54%	0.38%	-0.16%
2	2026-04-07	0.64%	0.54%	-0.09%
3	2026-03-19	—	0.64%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-30

0.54%

0.38%

-0.16%

2026-04-07

0.64%

0.54%

-0.09%

2026-03-19

—

0.64%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.3	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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.4	5.9	[email protected]
6.3	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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.4	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.3

3.1

MEDIUM

CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.4

5.9

[email protected]

6.3

3.1

MEDIUM

CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.4

5.9

[email protected]

Affected software / configurations for CVE-2023-21860

Vendor	Product	Version	Raw CPE
oracle	mysql_cluster	>= 7.4.0, <= 7.4.38	cpe:2.3:a:oracle:mysql_cluster::::::::
oracle	mysql_cluster	>= 7.5.0, <= 7.5.28	cpe:2.3:a:oracle:mysql_cluster::::::::
oracle	mysql_cluster	>= 7.6.0, <= 7.6.24	cpe:2.3:a:oracle:mysql_cluster::::::::
oracle	mysql_cluster	>= 8.0.0, <= 8.0.31	cpe:2.3:a:oracle:mysql_cluster::::::::

References for CVE-2023-21860

URL	Tags
https://www.oracle.com/security-alerts/cpujan2023.html	Patch Vendor Advisory

URL

CVE-2023-21860

Exploit prediction scoring system (EPSS) score for CVE-2023-21860

Common vulnerability scoring system (CVSS) metrics for CVE-2023-21860

Weakness enumeration for CVE-2023-21860

Affected software / configurations for CVE-2023-21860

References for CVE-2023-21860