What the vendor says is affected
- Windows 10 Version 1809 for 32-bit Systems
- Windows 10 Version 1809 for x64-based Systems
- Windows Server 2019
- Windows Server 2019 (Server Core installation)
- Windows Server 2022
- Windows Server 2022 (Server Core installation)
- Windows 10 Version 21H2 for 32-bit Systems
- Windows 10 Version 21H2 for ARM64-based Systems
- Windows 10 Version 21H2 for x64-based Systems
- Windows 10 Version 22H2 for x64-based Systems
- Windows 10 Version 22H2 for ARM64-based Systems
- Windows 10 Version 22H2 for 32-bit Systems
- Windows Server 2025 (Server Core installation)
- Windows 11 Version 25H2 for ARM64-based Systems
- Windows 11 Version 25H2 for x64-based Systems
- Windows 11 Version 23H2 for ARM64-based Systems
- Windows 11 Version 23H2 for x64-based Systems
- Windows 11 Version 24H2 for ARM64-based Systems
- Windows 11 Version 24H2 for x64-based Systems
- Windows Server 2025
- Windows 11 version 26H1 for x64-based Systems
- Windows 11 Version 26H1 for ARM64-based Systems
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
Versions the vendor lists as fixed
- 10.0.17763.8880
- 10.0.20348.5256
- 10.0.19044.7417
- 10.0.19045.7417
- 10.0.26100.32995
- 10.0.26200.8655
- 10.0.22631.7219
- 10.0.26100.8655
- 10.0.28000.2269
- 10.0.14393.9234
- 6.2.9200.26132
- 6.3.9600.23228
What the vendor recommends
To help protect against this vulnerability prior to installing the June 2026 security updates for your operating system, you may need to modify the MaxRequestBytes registry value used by the Windows HTTP stack if it isn't set to the default value. Note Systems using the default value (16384 bytes / 16 KB) are not impacted by this vulnerability. Configurations that increase this value beyond safe l Install KB5094123. Install KB5094128. Install KB5094127. Install KB5094125. Install KB5094126. Install KB5093998. Install KB5095051. Install KB5094122. Install KB5094042. Install KB5094041.
Review the complete instructions on the vendor's siteWhen this advisory changed
- Published by Microsoft Security Response Center
The publication date reported by the vendor.
- Added to SecurityAlert
We collected the advisory from the official source.