Skip to content
major vulnerability· requires attention

A remote code execution bug in Microsoft Windows NLB affects widely used Windows servers; high-impact, enterprise-wide risk warranting broad alerting.

Systems

CVE-2026-83862

9.8
Critical
EPSS 0.65%Patch availableOct 15, 2026

Use-after-free in Windows Network Load Balancing enables remote code execution.

common questions

Is CVE-2026-83862 being exploited?

Not confirmed. CVE-2026-83862 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. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.

How severe is CVE-2026-83862?

CVE-2026-83862 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-83862?

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

What does CVE-2026-83862 affect?

CVE-2026-83862 affects Microsoft Windows Network Load Balancing (NLB), Windows Server (NLB-enabled hosts). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-83862?

Deploy Microsoft's security update immediately; isolate or block NLB hosts if patching delayed.

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

executive summary
technical analysis
affected
Microsoft Windows Network Load Balancing (NLB)Windows Server (NLB-enabled hosts)
impact

Remote code execution as SYSTEM on NLB-enabled Windows hosts via crafted network traffic, enabling full system compromise.

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