Cyber Resilience

CVE-2025-21210

Microsoft Windows 10 1507 ≤ 10.0.10240.20890

Published
14 January 2025
Modified
27 January 2025
Patch / advisory
CVSS Score v3.1 4.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.011 64th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2025-21210 is a medium-severity Failing Open (CWE-636) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 4.2 (Medium).

Operationally, ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CP-12 (Safe Mode) and SC-24 (Fail in Known State) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Windows BitLocker Information Disclosure Vulnerability

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-43532Same product: Microsoft Windows 10 1507
CVE-2025-21243Same product: Microsoft Windows 10 1507
CVE-2024-49138Same product: Microsoft Windows 10 1507
CVE-2025-21251Same product: Microsoft Windows 10 1507
CVE-2025-21240Same product: Microsoft Windows 10 1507
CVE-2025-21223Same product: Microsoft Windows 10 1507
CVE-2024-49122Same product: Microsoft Windows 10 1507
CVE-2024-49088Same product: Microsoft Windows 10 1507
CVE-2024-43627Same product: Microsoft Windows 10 1507
CVE-2025-21261Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.20890 · ≤ 10.0.10240.20890
microsoft
windows 10 1607
≤ 10.0.14393.7699 · ≤ 10.0.14393.7699
microsoft
windows 10 1809
≤ 10.0.17763.6775 · ≤ 10.0.17763.6775
microsoft
windows 10 21h2
≤ 10.0.19044.5371
microsoft
windows 10 22h2
≤ 10.0.19045.5371
microsoft
windows 11 22h2
≤ 10.0.22621.4751
microsoft
windows 11 23h2
≤ 10.0.22631.4751
microsoft
windows 11 24h2
≤ 10.0.26100.2894
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+5 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.2.1
  • V7.4.1
  • V8.3.3
  • V10.3.4

Mitigating Controls (NIST 800-53 r5) AI

SC-24 directly requires the system to fail to a known state that preserves security properties, structurally stopping fallback to a less-secure mode.

SI-17 mandates explicit fail-safe procedures that activate on indicated failures, preventing the insecure fallback behavior.

CP-12 forces entry into a safe mode on detected conditions, limiting exposure but not covering every failure path.

SA-8 requires application of engineering principles that include fail-secure design, reducing the likelihood the weakness is introduced.

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.PS-06 mostly match
prevents

Secure-development practices explicitly include designing error and failure handling to remain in a secure state.

PR.AA-05 partial match
prevents

Least-privilege policy and enforcement directly counters the permissive-access fallback example in the CWE.

PR.PS-01 partial match
prevents

Hardened baselines and configuration management reduce the chance that error paths default to insecure settings.

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.

none

The control forces an explicit evaluation step before any response, reducing the chance that a failure condition will default to an unsafe open state.

References