Cyber Resilience

CVE-2025-21520

LPE in Oracle Mysql Cluster 7.6.0 – 7.6.32

Published
21 January 2025
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 1.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-21520 is a low-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Oracle Mysql Cluster. Its CVSS base score is 1.8 (Low).

Operationally, ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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).

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-60331Same product: Oracle Mysql Cluster
CVE-2025-21523Same product: Oracle Mysql Server
CVE-2026-46936Same product: Oracle Mysql Cluster
CVE-2025-21543Same product: Oracle Mysql Cluster
CVE-2025-30682Same product: Oracle Mysql Server
CVE-2026-47012Same product: Oracle Mysql Cluster
CVE-2025-21566Same product: Oracle Mysql Server
CVE-2026-61108Same product: Oracle Mysql Cluster
CVE-2025-21584Same product: Oracle Mysql Server
CVE-2026-60189Same product: Oracle Mysql Cluster

Affected Assets

oracle
mysql cluster
7.6.0 — 7.6.32 · 8.0.0 — 8.0.40 · 8.4.0 — 8.4.3
oracle
mysql server
8.0.0 — 8.0.40 · 8.4.0 — 8.4.3 · 9.0.0 — 9.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization policies on MySQL Server resources so that even a high-privileged local account cannot read data outside its permitted scope.

prevent

Requires that MySQL accounts and OS accounts operate with only the minimum privileges needed, reducing the impact surface of the CWE-732 permission flaw.

prevent

Mandates secure baseline configuration settings for MySQL Server and host file/DB permissions, directly mitigating incorrect permission assignments that enable the described data read.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires defining, enforcing, and reviewing access permissions and least privilege on resources.

PR.PS-01 mostly match
prevents

Hardened baselines and configuration management explicitly include correct permission settings for critical resources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.

prevents

Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.

prevents

Documented authorization, expiry rules, and audit logging of privileged accounts make it harder for critical resources to retain overly permissive or stale permission assignments.

prevents

Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.

prevents

Enforcing differentiated permissions on the source-code repository and program listings stops the assignment of overly broad default or inherited permissions to critical resources.

prevents

By defining and enforcing secure permission settings in configuration templates, the control reduces the likelihood that critical resources receive incorrect permission assignments.

References