CVE-2025-21220
Microsoft Windows 10 1507 ≤ 10.0.10240.20890
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-21220 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft Message Queuing is affected by an information disclosure vulnerability tracked as CVE-2025-21220. This flaw, which carries a CVSS score of 7.5, stems from the use of uninitialized resources as indicated by CWE-908 and allows unauthorized access to sensitive information over a network connection.
An unauthenticated attacker with network access can exploit this vulnerability due to its low attack complexity and lack of required user interaction, resulting in the disclosure of high-value confidential data without impacting integrity or availability.
The Microsoft Security Response Center provides guidance on this issue through its update guide at the referenced advisory URL. The associated EPSS score has remained low, with a current value of 0.0136 and a peak of 0.0193.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-2289
Vulnerability Data
Microsoft Message Queuing Information Disclosure Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
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.
Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
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.
Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.