Skip to main content
CVE-2025-21520VulnerabilityPublished Updated

CVE-2025-21520: Oracle MySQL Cluster · Incorrect Permissions

Affects Oracle MySQL ClusterSource CVE Database V5

0

Not known to be exploited · CVSS 1.8 Low · fixed in 9.1.1 : update Oracle MySQL Cluster when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
1.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.1.1, 8.4.4, 8.0.41
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade com.oracle/mysql-cluster to 9.1.1, 8.4.4 or 8.0.41.

Affected software

ProductAffectedFixed in
Mavencom.oracle/mysql-clusterpkg:maven/com.oracle/mysql-clusterOther threatsAffected
  • <8.0.41
  • <8.4.4
  • <9.1.1
Fixed in
  • 8.0.41
  • 8.4.4
  • 9.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Restrict and monitor high-privilege access to MySQL Cluster infrastructure, ensuring only authorized personnel have such access. 2) Enforce strict access controls and multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. 3) Conduct user awareness training to minimize the risk of social engineering or inadvertent user interaction that could facilitate exploitation. 4) Regularly audit MySQL Cluster configurations and permissions to detect and remediate any excessive privileges or misconfigurations. 6) Implement network segmentation to isolate MySQL Cluster infrastructure from less trusted network zones. 7) Monitor logs and alerts for unusual access patterns or attempts to exploit the vulnerability. These steps go beyond generic advice by focusing on the specific conditions required for exploitation and the nature of the vulnerability.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options). Supported versions that are affected are 8.0.40 and prior, 8.4.3 and prior and 9.1.0 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 1.8 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N).

References

Community reviews

Loading reviews…