Cyber Resilience

CVE-2025-21210

Medium

Published: 14 January 2025

Published
14 January 2025
Modified
27 January 2025
KEV Added
Patch
CVSS Score v3.1 4.2 CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0024 47.5th percentile
Risk Priority 9 60% EPSS · 20% KEV · 20% CVSS

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 at the 47.5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability details

Windows BitLocker Information Disclosure Vulnerability

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

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

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-636

Ensures audit logging continues on primary failure instead of failing open with no logging capability.

addresses: CWE-636

Supports failing securely by requiring alerts and configurable actions (e.g., shutdown) when the audit mechanism fails instead of continuing without it.

addresses: CWE-636

Entering safe mode when conditions are detected prevents failing open and continuing normal operation in a potentially exploitable state.

addresses: CWE-636

Ensures security functions remain enforced via alternatives instead of defaulting to an insecure state when the primary means fails.

addresses: CWE-636

Fail-safe-defaults principle prevents systems from failing open.

addresses: CWE-636

Directly requires transition to a known (secure) state on failure, preventing fail-open behavior.

addresses: CWE-636

Standby components and explicit exchange criteria enforce a controlled, secure failover instead of failing open.

addresses: CWE-636

Directly implements fail-safe (fail-closed/secure) behavior on indicated failures, preventing the system from defaulting to an insecure open state.

References