Skip to content
major vulnerability· requires attention

Windows Shell RCE affects widely deployed Windows endpoints/servers; critical 9.8 CVSS and potential for large-scale disruption.

Systems

CVE-2026-83782

9.8
Critical
EPSS n/aPatch availableOct 15, 2026

Windows Shell heap overflow enables remote code execution.

common questions

Is CVE-2026-83782 being exploited?

Not confirmed. CVE-2026-83782 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-83782?

CVE-2026-83782 is rated Critical with a CVSS score of 9.8. 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-2026-83782?

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

What does CVE-2026-83782 affect?

CVE-2026-83782 affects Microsoft Windows (Windows Shell). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-83782?

Apply Microsoft security update immediately; isolate or block exposed systems.

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

executive summary
technical analysis
affected
Microsoft Windows (Windows Shell)
impact

Remote code execution over network allowing attackers to run arbitrary code and potentially gain full system control.

action required

Immediate action required

affected versions
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.9612
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.7807
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19044.7807
Microsoft Windows 11 version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7652
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7652
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.9711
Microsoft Windows 11 Version 25H2
  • affected>= 10.0.26200.0 and < 10.0.26200.9711
Microsoft Windows 11 version 26H1
  • affected>= 10.0.28000.0 and < 10.0.28000.3231
Microsoft Windows 11 Version 26H2
  • affected>= 10.0.26300.0 and < 10.0.26300.9711
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.26434
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.23470
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.23470
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.26434
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.9612
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.9612
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5761
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33650
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33650

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.

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
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free