Skip to content
major vulnerability· requires attention

Remote code execution in a Microsoft Windows server component (Work Folders); high-impact RCE in widely deployed enterprise OS.

Systems

CVE-2026-71336

8.8
High
EPSS 0.85%Patch availableSep 10, 2026

Authenticated RCE via integer overflow in Windows Work Folders.

common questions

Is CVE-2026-71336 being exploited?

Not confirmed. CVE-2026-71336 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.85% probability of exploitation in the next 30 days.

How severe is CVE-2026-71336?

CVE-2026-71336 is rated High with a CVSS score of 8.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-71336?

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

What does CVE-2026-71336 affect?

CVE-2026-71336 affects Microsoft Windows Server (Work Folders service). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71336?

Apply Microsoft security update to affected servers immediately.

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

executive summary
technical analysis
affected
Microsoft Windows Server (Work Folders service)
impact

Authenticated network attacker can trigger an integer overflow in Work Folders to achieve remote code execution on affected Windows servers.

action required

Immediate action required

affected versions
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.9512
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.9245
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.23397
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.23397
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.9512
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.9512
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9245
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9245
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5622
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33438
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33438

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