Security advisory
WindowsCriticalResolved

Microsoft Ships KB5083769 for Windows 11 25H2, Patching Kernel, WebView2 and Print Spooler Flaws

The cumulative update patches privilege-escalation, remote-code-execution and security-bypass vulnerabilities and is recommended for immediate enterprise deployment.

Emanuel De AlmeidaApr 15, 2026, 7:46 PM5 min read
Severity
Critical
Status
Resolved
Entity
Microsoft
Confirmed by
KB5083769 update documentation

Microsoft released KB5083769 on April 14, 2026, a critical cumulative security update for Windows 11 version 25H2 that also applies to version 24H2. According to the update documentation, it addresses six vulnerabilities across the Windows Kernel, Microsoft Edge WebView2, the Windows Graphics Component, the Common Log File System and the Print Spooler service.

The vulnerabilities could allow attackers to escalate privileges to SYSTEM, execute arbitrary code or bypass security features, so administrators are advised to deploy the update promptly across Windows 11 fleets.

Key takeaways

  • KB5083769 is a critical security update released on April 14, 2026 for Windows 11 25H2 and 24H2.
  • It patches six CVEs (CVE-2026-20001 through CVE-2026-20006) across kernel, WebView2, graphics, CLFS and Print Spooler components.
  • After install, systems report build 26200.8246 (25H2) or 26100.8246 (24H2).
  • The update is delivered via Windows Update, WSUS, SCCM, Intune and the Microsoft Update Catalog and requires a restart.
  • A documented install failure (error 0x80070070) can occur on systems with less than 2 GB free disk space.

Affected

Vendors
Microsoft
Products
Windows 11 Version 25H2Windows 11 Version 24H2
Geography
Global
CVEs
CVE-2026-20001CVE-2026-20002CVE-2026-20003CVE-2026-20004CVE-2026-20005CVE-2026-20006

What the update does

KB5083769 is a critical cumulative security update for Windows 11 version 25H2, released on April 14, 2026. The documentation states it also applies to version 24H2 and addresses multiple vulnerabilities that could let attackers execute arbitrary code, escalate privileges or bypass security features.

After installation, systems report operating-system build 26200.8246 on version 25H2 and 26100.8246 on version 24H2. The update is cumulative, so it also includes prior fixes for the affected branches.

  • Release date: April 14, 2026
  • Post-install builds: 26200.8246 (25H2) / 26100.8246 (24H2)

Vulnerabilities addressed

According to the update documentation, KB5083769 resolves six tracked vulnerabilities across core Windows components:

  • CVE-2026-20001 and CVE-2026-20002 — Windows Kernel privilege escalation via buffer overflow conditions in kernel-mode drivers (ntoskrnl.exe and related modules), potentially reaching SYSTEM-level access.
  • CVE-2026-20003 — Microsoft Edge WebView2 remote code execution through specially crafted web content in applications embedding WebView2 controls.
  • CVE-2026-20004 — Windows Graphics Component memory corruption affecting win32k.sys and DirectX components, potentially leading to arbitrary code execution.
  • CVE-2026-20005 — Windows Common Log File System (CLFS) security feature bypass affecting the clfs.sys driver.
  • CVE-2026-20006 — Windows Print Spooler elevation of privilege affecting the spoolsv.exe service.

The documentation attributes the underlying issues to improper input validation and memory management, including insufficient bounds checking in kernel-mode drivers and inadequate validation of user-supplied graphics data.

  • Six CVEs: CVE-2026-20001 through CVE-2026-20006

Affected systems

The update applies to the following editions and architectures:

  • Windows 11 version 25H2 on x64 systems — build 26200.8246
  • Windows 11 version 25H2 on ARM64 systems — build 26200.8246
  • Windows 11 version 24H2 on x64 systems — build 26100.8246
  • Windows 11 version 24H2 on ARM64 systems — build 26100.8246

Deployment and verification

The update is distributed through Windows Update, the Microsoft Update Catalog (for offline installation), WSUS, Microsoft System Center Configuration Manager and Microsoft Intune. It is classified as a critical security update with automatic approval recommended for enterprise environments. A restart is required to complete installation.

Per the documentation, the package is approximately 890 MB for x64 systems and 720 MB for ARM64 systems, and systems need at least 2 GB of available disk space.

Verify installation with PowerShell

PowerShell
Get-HotFix -Id KB5083769

Get-WmiObject -Class Win32_QuickFixEngineering | Where-Object {$_.HotFixID -eq "KB5083769"}

Get-ComputerInfo | Select-Object WindowsVersion, WindowsBuildLabEx
  • Restart required to complete installation
  • Minimum 2 GB free disk space required

Known issues

The documentation lists several known issues administrators should account for during rollout:

  • Installation may fail with error 0x80070070 on systems with less than 2 GB of free disk space; free up space before retrying.
  • Temporary system slowdown can occur during installation, particularly on devices with traditional hard drives, and resolves after completion.
  • Some third-party antivirus products may need updates to remain compatible; check with the vendor if issues occur.

Rollback path

If persistent issues occur, the update can be removed via Settings > Windows Update > Update history > Uninstall updates.

Timeline

Apr 14, 2026
KB5083769 releasedMicrosoft releases KB5083769 as a critical security update for Windows 11 25H2 and 24H2, moving builds to 26200.8246 and 26100.8246.

Impact & actions

Unpatched Windows 11 25H2 and 24H2 systems remain exposed to privilege-escalation, remote-code-execution and security-bypass vulnerabilities across core OS components.

Security: Successful exploitation could grant SYSTEM-level access, execute arbitrary code or bypass security controls.

Recommended actions · High urgency

  1. 1Approve and deploy KB5083769 to Windows 11 25H2 and 24H2 systems
  2. 2Ensure at least 2 GB free disk space before installation to avoid error 0x80070070
  3. 3Schedule the required restart within maintenance windows
  4. 4Verify installation with Get-HotFix -Id KB5083769 and confirm build 26200.8246 / 26100.8246

Technical details

CVEs
CVE-2026-20001, CVE-2026-20002, CVE-2026-20003, CVE-2026-20004, CVE-2026-20005, CVE-2026-20006
Affected versions
Windows 11 25H2 (pre-26200.8246), Windows 11 24H2 (pre-26100.8246)
Patched versions
26200.8246, 26100.8246

Mitigations

  • Install KB5083769 via Windows Update, WSUS, SCCM, Intune or the Microsoft Update Catalog

Response

Customer guidance

Microsoft's documentation recommends prioritizing deployment of this critical update through standard Windows Update channels or enterprise management tools, with automatic approval recommended for enterprises.

FAQ

What does KB5083769 fix?

It addresses six vulnerabilities in Windows 11 25H2 and 24H2: Windows Kernel privilege escalation (CVE-2026-20001, CVE-2026-20002), Edge WebView2 remote code execution (CVE-2026-20003), Graphics Component memory corruption (CVE-2026-20004), Common Log File System security bypass (CVE-2026-20005) and Print Spooler elevation of privilege (CVE-2026-20006).

Which build does KB5083769 install?

After installation, Windows 11 version 25H2 reports build 26200.8246 and version 24H2 reports build 26100.8246.

How do I check if KB5083769 is installed?

Run Get-HotFix -Id KB5083769 in PowerShell, or check Settings > Windows Update > Update history. You can also confirm the build number with Get-ComputerInfo.

Why might installation fail with error 0x80070070?

That error indicates insufficient disk space. The update requires at least 2 GB of free space; run Disk Cleanup or remove unneeded files, then retry.

The bottom line

Microsoft's KB5083769, released April 14, 2026, patches six vulnerabilities in Windows 11 25H2 and 24H2 and updates systems to build 26200.8246 / 26100.8246.

What happens next

Administrators should approve and roll out the update across affected fleets, monitoring for the documented disk-space and antivirus-compatibility issues.

What to do

Deploy KB5083769 to Windows 11 25H2 and 24H2 systems and verify the resulting build number.

Reader reviews

Rate this articleBe the first to rate
No written reviews yetRate the article above, or be the first to share your experience.

Related articles