Cyber Resilience

CVE-2025-53803

Info Disclosure in Microsoft Windows 10 1507 ≤ 10.0.10240.21128

Published
09 September 2025
Modified
02 October 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0065 48th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-53803 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 48th 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 SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Generation of error message containing sensitive information in Windows Kernel allows an authorized attacker to disclose information locally.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance
Adversaries may gather information about the victim's host software that can be used during targeting.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
T1595 Active Scanning Reconnaissance
Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21313Same product: Microsoft Windows 10 1507
CVE-2024-29059Same product: Microsoft Windows 10 1507
CVE-2026-20838Same product: Microsoft Windows 11 23H2
CVE-2025-55676Same product: Microsoft Windows 11 24H2
CVE-2013-7331Same product: Microsoft Windows Server 2012
CVE-2024-28939Same vendor: Microsoft
CVE-2024-43636Same product: Microsoft Windows 10 1507
CVE-2024-43627Same product: Microsoft Windows 10 1507
CVE-2024-49046Same product: Microsoft Windows 10 1507
CVE-2024-43638Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.21128 · ≤ 10.0.10240.21128
microsoft
windows 10 1607
≤ 10.0.14393.8422 · ≤ 10.0.14393.8422
microsoft
windows 10 1809
≤ 10.0.17763.7792 · ≤ 10.0.17763.7792
microsoft
windows 10 21h2
≤ 10.0.19044.6332
microsoft
windows 10 22h2
≤ 10.0.19045.6332
microsoft
windows 11 22h2
≤ 10.0.22621.5909
microsoft
windows 11 23h2
≤ 10.0.22631.5909
microsoft
windows 11 24h2
≤ 10.0.26100.6508
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
≤ 10.0.14393.8422
+4 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)
  • V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

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 SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

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

Secure coding standards explicitly forbid exposing sensitive data in errors.

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References