CVE-2025-48813
Use of a key past its expiration date in Virtual Secure Mode allows an authorized attacker to perform spoofing locally.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.3
- CVSS vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
- EPSS probability
- 0.23%
- CWE
- CWE-324
- Published
- 2025-10-14
- Last modified
- 2026-03-13
Affected products
- Microsoft Windows 10 Version 1809
- Microsoft Windows 10 Version 21H2
- Microsoft Windows 10 Version 22H2
- Microsoft Windows 11 version 22H2
- Microsoft Windows 11 version 22H3
- Microsoft Windows 11 Version 23H2
- Microsoft Windows 11 Version 24H2
- Microsoft Windows 11 Version 25H2
Weakness type
Related vulnerabilities
- CVE-2026-39923 — Flarum < 1.8.16 Password Reset Token Expiry Bypass via POST /reset
- CVE-2026-54787 — sigstore-go fails to check signature timestamps against a signing key's validity period
- CVE-2026-52809 — Gogs: Password-reset tokens use account-activation lifetime, ignoring RESET_PASSWORD_CODE_LIVES
- CVE-2025-33012 — IBM Db2 improper account lockout
- CVE-2023-5342 — Shim: expired secure boot certificate
- CVE-2025-2291 — PgBouncer default auth_query does not take Postgres password expiry into account
- CVE-2025-31123 — Zitadel Expired JWT Keys Usable for Authorization Grants
- CVE-2024-7318 — Keycloak-core: one time passcode (otp) is valid longer than expiration timeseverity