CVE-2025-48813
Microsoft Windows 10 1809 ≤ 10.0.17763.7919
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-48813 is a medium-severity Use of a Key Past its Expiration Date (CWE-324) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 14th 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 IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-34355
Vulnerability Data
Use of a key past its expiration date in Virtual Secure Mode allows an authorized attacker to perform spoofing locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SC-12 requires establishing and managing cryptographic keys including distribution, storage, access and destruction, which directly enforces expiration and rotation policies.
IA-5 requires managing authenticators (including passwords and tokens) with verification, distribution and revocation steps that cover expiration enforcement.
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.
Lifecycle management of cryptographic assets directly includes enforcing key expiration and rotation.
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.
Use-of-cryptography control explicitly covers key lifecycle management including expiration and rotation.
Authentication information policy should mandate key rotation and expiry, directly preventing use of expired keys.
Change-management processes can trigger key rotation, but do not inherently enforce cryptographic expiry rules.
Secure authentication requires cryptographic keys to be replaced before expiry, mitigating the weakness.