Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Identify exposed Windows HTTP listener
  2. Delivery
    Craft request with overflowing length field
  3. Exploit
    Send to HTTP.sys over TCP/80 or 443
  4. Install
    Integer wrap undersizes kernel heap allocation
  5. C2
    Overwrite adjacent pool memory
  6. Execute
    Hijack kernel control flow as SYSTEM
  7. Impact
    Deploy implant or pivot internally

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of any Windows host running an HTTP.sys-backed service reachable over the network, per the CVSS AV:N/AC:L/PR:N/UI:N vector. The practical limiting factor is exposure of an HTTP/HTTPS listener bound to HTTP.sys (IIS, WinRM over HTTP, WSDAPI, SSDP, or third-party services using the HTTP Server API) on a network path reachable from the attacker; hosts with no such listener bound, or with TCP/80 and TCP/443 firewalled to trusted sources only, are not exploitable. The description does not call out a specific protocol feature (e.g., HTTP/2, chunked encoding, range requests) as the trigger, so feature-level scoping cannot be confirmed from the available data.

Impact

All CVSS sub-metrics point to a top-tier risk: AV:N/AC:L/PR:N/UI:N means a remote, unauthenticated attacker can reach the bug over the network with low complexity, and C:H/I:H/A:H reflects full compromise of confidentiality, integrity, and availability. EPSS and SSVC values were not provided in the input, so probabilistic exploitation likelihood and automatability cannot be quantified here. The vulnerability is not listed in CISA KEV at the time of analysis and no public exploit code has been identified, which slightly tempers immediate urgency, but the kernel-mode attack surface and historical wormability of HTTP.sys bugs justify treating this as a P0 patching priority regardless of the absent telemetry. The single available reference is the Microsoft MSRC advisory, so detailed root-cause and exploit-status data beyond the description and CVSS vector are not independently confirmed.

Exploit ScenarioDerived

An attacker on the internet sends a single specially crafted HTTP request to a vulnerable IIS server or any Windows host exposing an HTTP.sys-backed listener, with header or chunked-body length fields chosen to wrap an internal size calculation. The undersized heap allocation is then overwritten by attacker-controlled bytes, corrupting kernel pool memory and ultimately yielding code execution in the SYSTEM context. No public exploit has been identified at the time of analysis, but the CVSS profile (AV:N/AC:L/PR:N/UI:N) and HTTP.sys history make pre-auth, scriptable mass exploitation plausible once a working trigger is published.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 09, 2026

Remote code execution in Microsoft Windows HTTP.sys allows unauthenticated network attackers to execute arbitrary code by triggering an integer overflow that leads to heap-based memory corruption. The flaw carries a CVSS 9.8 rating reflecting network reachability, no privileges, and no user interaction, and impacts the kernel-mode HTTP listener used by IIS and any Windows service relying on the HTTP Server API. No public exploit has been identified at the time of analysis and CISA KEV does not list it, but the wormable profile of HTTP.sys flaws warrants urgent patching.

RemediationAI

Apply the Microsoft security update referenced in the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47291) for each affected Windows build as the primary fix; an exact fix version was not provided in the input data, so consult the advisory for the specific KB articles per SKU. Where patching cannot be completed immediately, restrict inbound TCP/80 and TCP/443 to HTTP.sys-backed services using host or network firewalls, terminate TLS and HTTP parsing on a non-Windows reverse proxy in front of IIS so malformed requests never reach the kernel driver, and disable optional HTTP.sys features such as HTTP/2 or response caching if the advisory identifies them as the trigger surface - note that proxy fronting can break NTLM/Kerberos pass-through and disabling HTTP/2 will reduce performance for modern clients. Audit and disable any unused HTTP Server API consumers (WinRM, WSDAPI, SSDP) on servers that do not require them.

Affected VersionsENISA

Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9234 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9234, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9234
microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269, Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_server_2012_6_2_9200_26132 fix: Windows Server 2012 6.2.9200.26132, Windows Server 2012 (Server Core installation) 6.2.9200.26132
microsoft windows_server_2012_r2_6_3_9600_23228 fix: Windows Server 2012 R2 6.3.9600.23228, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23228
microsoft windows_server_2016_10_0_14393_9234 fix: Windows Server 2016 10.0.14393.9234, Windows Server 2016 (Server Core installation) 10.0.14393.9234
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
euvd windows_10_version_1607 fix: 10.0.14393.9234
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012 fix: 6.2.9200.26132
euvd windows_server_2012_r2 fix: 6.3.9600.23228
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23228
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26132
euvd windows_server_2016 fix: 10.0.14393.9234
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9234
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 33 packages in microsoft, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

HTTP.sys is the Windows kernel-mode driver that parses and queues HTTP/HTTPS requests on behalf of IIS, WinRM, WSDAPI, SSDP, and various third-party services using the HTTP Server API. CWE-122 (Heap-based Buffer Overflow), triggered here through an integer overflow or wraparound in size calculations, occurs when arithmetic on a request-derived length wraps past INT_MAX or SIZE_MAX, causing a downstream allocation to be sized smaller than the data subsequently copied into it. Because HTTP.sys executes in kernel context (System), successful memory corruption typically yields SYSTEM-level code execution and is historically wormable, as seen in prior HTTP.sys issues such as CVE-2021-31166 and CVE-2022-21907.

Know when Windows 10 1607 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 8.5 HIGH

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Jun 09, 2026 - 19:03 EUVD
CVE Published
Jun 09, 2026 - 17:17 nvd
CRITICAL 9.8

DescriptionCVE.org

Integer overflow or wraparound in Windows HTTP.sys allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

A critical remote code execution vulnerability in Windows HTTP.sys (CVE-2026-47291) exposes all IIS and HTTP Server API-dependent services to complete system compromise through unauthenticated network access, with no vendor patch currently available. The vulnerability's wormable characteristics mean rapid propagation is possible once exploitation begins. Organizations must immediately inventory affected systems and implement emergency compensating controls while awaiting vendor patching.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to HTTP.sys listeners through firewalls and network segmentation, deploy Web Application Firewall (WAF) rules on IIS endpoints, disable HTTP Server API services not operationally required, implement EDR tooling with monitoring for HTTP.sys process anomalies, and restrict administrative access to affected systems. These controls reduce but do not eliminate risk-emergency patching is critical upon vendor availability.

Threat Intelligence Overview

EPSS Score
0.2%
Top 60% exploitable
Threat Intel
1
1 sources
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More Likely
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment NEWS MSRC GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

69
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy