A researcher published full technical details and proof-of-concept code for a Windows HTTP.sys vulnerability on September 2026. Tracked as CVE-2026-62735, the flaw carries a 7.8 CVSS score. It lets a local attacker climb to SYSTEM privileges. Microsoft patched it in the August 2026 Patch Tuesday.
- CVE: CVE-2026-62735
- CVSS: 7.8 (High · CVSSv3)
- Product: Microsoft Windows 10 Version 1607
- Affected: 10.0.14393.0, 10.0.17763.0, 10.0.19044.0, 10.0.19045.0, 10.0.22631.0, 10.0.26100.0 (+5 more)
- Impact: Windows HTTP.sys Elevation of Privilege Vulnerability
- Status: No confirmed exploitation yet
- Patched in: 10.0.14393.9418, 10.0.17763.9121, 10.0.19044.7663, 10.0.19045.7663 (+8 more)
- EPSS: 0.5% (30-day)
- Action: Update to 10.0.14393.9418, 10.0.17763.9121, 10.0.19044.7663, 10.0.19045.7663 (+8 more) now
Why this matters
HTTP.sys is a kernel-mode driver at the heart of Windows networking. So a bug here runs with the highest privileges. This Windows HTTP.sys vulnerability turns a low-privileged user into SYSTEM. That level of access allows full host control. Now that details and a PoC are public, exploit risk rises sharply.
How the attack works
The security flaw stems from an integer overflow inside the UlpCreateInternalResponseOld function. When calculating the total number of header bytes, the driver fails to prevent integer wrap-around. Consequently, HTTP.sys allocates a smaller nonpaged-pool buffer than the headers actually require.
The CVE-2026-62735 PoC process sends an oversized HTTP response containing nearly 70,000 custom header entries. Next, the user-mode process transmits this response to the kernel driver using a specific IOCTL request. The undersized buffer triggers a heap overflow during header copying. Ultimately, this memory corruption allows the attacker to execute code with elevated SYSTEM privileges.
The researcher demonstrated the crash using a local proof-of-concept. Siyeon Wi first showed the bug at Pwn2Own Berlin 2026. Notably, exploitation needs local access and low privileges, but no user interaction.
Affected versions
The flaw affects a wide range of Windows builds. These include Windows 10, Windows 11, and Windows Server 2012 through 2025. The public demonstration targeted Windows 11 25H2.
Patch and mitigation steps
Apply the August 2026 security update now. Microsoft published no workaround, so patching is the only fix. Check the official Microsoft advisory for the correct KB per build. Where patching must wait, limit local logon rights on shared hosts.
Public technical details and proof-of-concept
This premium content is securely locked. You must upgrade your subscription to access the full threat intelligence report, including detailed mitigation steps, deep-dive analysis, and active exploitation metrics. Your attempt to inspect the DOM will only reveal this placeholder text. Please support our work to read the actual coverage.
Unlock Premium Threat Intelligence
This is a premium content. Upgrade to Pro or Team to unlock full access and remove all reading restrictions.