Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-48813: CWE-324: Use of a Key Past its Expiration Date in Microsoft Windows 11 Version 25H2

0
Medium
VulnerabilityCVE-2025-48813cvecve-2025-48813cwe-324
Published: Tue Oct 14 2025 (10/14/2025, 17:00:53 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 11 Version 25H2

Description

Use of a key past its expiration date in Virtual Secure Mode allows an authorized attacker to perform spoofing locally.

AI-Powered Analysis

AILast updated: 01/02/2026, 22:19:40 UTC

Technical Analysis

CVE-2025-48813 is a vulnerability classified under CWE-324, which pertains to the use of cryptographic keys beyond their expiration date. Specifically, this issue affects Microsoft Windows 11 Version 25H2 (build 10.0.26200.0), where Virtual Secure Mode (VSM) improperly accepts keys that have expired. VSM is a security feature designed to isolate sensitive processes and data from the rest of the operating system, leveraging hardware virtualization to protect cryptographic keys and other secrets. The vulnerability allows an authorized local attacker with low privileges to exploit the acceptance of expired keys to perform spoofing attacks. Spoofing in this context means the attacker can impersonate trusted components or processes by leveraging cryptographic keys that should no longer be valid, potentially bypassing security controls that rely on key validity. The CVSS v3.1 base score is 6.3 (medium severity), reflecting that the attack vector is local (AV:L), requires high attack complexity (AC:H), low privileges (PR:L), and no user interaction (UI:N). The impact on confidentiality and integrity is high (C:H/I:H), but availability is not affected (A:N). No known exploits are currently reported in the wild, and no patches have been linked yet, indicating that mitigation relies on vendor updates and defensive measures. The vulnerability was reserved in May 2025 and published in October 2025, showing a relatively recent discovery. The flaw highlights the importance of proper cryptographic key lifecycle management within secure environments like VSM to prevent misuse of expired credentials.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality and integrity of sensitive data and operations protected by Virtual Secure Mode on Windows 11 25H2 systems. Attackers with local access could impersonate trusted system components or escalate privileges by exploiting expired keys, potentially leading to unauthorized access to protected secrets or bypassing security mechanisms. This could affect sectors handling sensitive personal data (e.g., finance, healthcare), critical infrastructure, and government systems that rely on Windows 11 25H2 with VSM enabled. Although exploitation requires local access and is complex, insider threats or attackers who have gained initial footholds could leverage this vulnerability to deepen their control or evade detection. The absence of availability impact means systems remain operational but potentially compromised in trustworthiness. The medium severity suggests a moderate but significant risk, especially in environments where strict cryptographic protections are essential. European organizations must be vigilant in monitoring local privilege escalations and cryptographic anomalies to mitigate potential exploitation.

Mitigation Recommendations

1. Apply official Microsoft patches promptly once released for Windows 11 Version 25H2 to address the expired key acceptance issue in VSM. 2. Enforce strict cryptographic key lifecycle policies, ensuring keys are revoked and removed immediately upon expiration to prevent reuse. 3. Monitor and audit local system activities for unusual cryptographic operations or attempts to use expired keys, leveraging endpoint detection and response (EDR) tools with capabilities to detect anomalies in VSM-related processes. 4. Limit local access to systems running Windows 11 25H2 with VSM enabled by enforcing strong access controls and minimizing the number of users with local privileges. 5. Employ application whitelisting and integrity monitoring to detect unauthorized modifications or spoofing attempts of trusted components. 6. Educate system administrators and security teams about the risks of key misuse and the importance of timely patching and key management. 7. Consider deploying additional hardware-based security modules or trusted platform modules (TPMs) that enforce stricter key validation policies beyond software controls. 8. Regularly review and update security configurations related to VSM and cryptographic services to align with best practices and vendor recommendations.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2025-05-26T17:09:49.056Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ee85833dd1bfb0b7e3e65b

Added to database: 10/14/2025, 5:16:51 PM

Last enriched: 1/2/2026, 10:19:40 PM

Last updated: 1/18/2026, 8:05:55 AM

Views: 76

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats