CVE-2025-29809
Published: 08 April 2025
Summary
CVE-2025-29809 is a high-severity Insecure Storage of Sensitive Information (CWE-922) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 7.1 (High).
Operationally, ranked in the top 24.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2025-29809 is an insecure storage of sensitive information vulnerability in the Windows Kerberos component. It is tracked under CWE-922 and carries a CVSS 3.1 base score of 7.1, reflecting local attack vector, low attack complexity, and low privileges required.
An authorized local attacker can exploit the flaw to bypass a security feature, resulting in high impact to confidentiality and integrity while leaving availability unaffected. No user interaction is needed for successful exploitation.
Microsoft has published an advisory for CVE-2025-29809 that includes mitigation guidance. The current EPSS score of 0.0088 and peak of 0.0140 do not indicate a material rise warranting renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-10125
Vulnerability details
Insecure storage of sensitive information in Windows Kerberos allows an authorized attacker to bypass a security feature locally.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
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.
Tracking information locations and access supports secure storage practices instead of insecure ones.
Establishing an alternate site with equivalent protections directly mitigates insecure storage of sensitive backup information.
Requiring protection of backup information directly addresses insecure storage of sensitive data in backups.
Policy explicitly addresses insecure storage of CUI on external systems, requiring compliant handling and protections.
Proper categorization drives selection of storage controls that keep sensitive information from being stored insecurely.
The control explicitly requires secure storage mechanisms for sensitive information, closing the insecure-storage weakness class.
Storing information as fragments on distinct components is an architectural control that avoids insecure single-location storage of the complete sensitive data set.
OPSEC requirements improve handling and storage practices for sensitive supply-chain information.