Skip to content
vulnerability

CVE-2025-62215

7.0
High
KEV · Exploited in wildEPSS 4%Patch available

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.

exploited
Yes, in CISA KEV since 12 Nov 2025fix by 3 Dec 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 4.5%
Published 11 Nov 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: noAV · localCWE-362· Common WeaknessCWE-415· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexityhighprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-62215 being exploited?

Yes. CVE-2025-62215 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-62215?

CVE-2025-62215 is rated High with a CVSS score of 7.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-62215?

Yes. A fix has been recorded for CVE-2025-62215. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-62215 affect?

CVE-2025-62215 affects microsoft:windows_10_1809, microsoft:windows_10_21h2, microsoft:windows_10_22h2, microsoft:windows_11_23h2, and 6 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_23h2microsoft:windows_11_24h2microsoft:windows_11_25h2microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2microsoft:windows_server_2025
affected versions
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.8027
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.6575
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.6575
Microsoft Windows 11 version 22H3
  • affected>= 10.0.22631.0 and < 10.0.22631.6199
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.6199
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.7171
Microsoft Windows 11 Version 25H2
  • affected>= 10.0.26200.0 and < 10.0.26200.7171
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.8027
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.8027
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.4405
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • affected>= 10.0.25398.0 and < 10.0.25398.1965
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.7171
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.7171

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 on Exploit-DB · 7 GitHub proofs of concept

Exploit-DB

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 12 Nov 2025 (SSVC 2.0.3).

timeline

  1. 11 Nov 2025Published
  2. 12 Nov 2025Added to CISA KEV (exploited in the wild) · same day later
  3. 12 Nov 2025CISA SSVC assessment: exploitation active · same day later
  4. 18 Nov 2025First public exploit or proof of concept · 6 days later
  5. 3 Dec 2025CISA remediation due date (US federal agencies) · 15 days later
  6. 26 Feb 2026CVE record last updated · 86 days (about 3 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 1 patch, 1 link
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-62215
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-62215

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved