You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
invoke webrequest
About this tag
The tag invoke webrequest covers recent security changes to the PowerShell 5.1 cmdlet Invoke-WebRequest, specifically a December 2025 update (KB5074204) that introduces a confirmation prompt before parsing web content that could execute scripts. This change, linked to CVE-2025-54100, applies to hotpatch-enrolled Windows 11 devices and aims to prevent remote code execution. Discussions include the prompt behavior, the UseBasicParsing parameter as a workaround, and implications for automation and interactive use. The tag is relevant for IT administrators and PowerShell users managing security updates and script execution risks.
Microsoft has quietly released KB5074204, a targeted security update for Windows PowerShell 5.1 that injects a behavioral safeguard into the frequently abused web‑facing cmdlet pipeline: after installation, the Invoke‑WebRequest command now displays an explicit confirmation prompt warning of the...
Windows PowerShell is now pausing to warn users when web content fetched with Invoke-WebRequest could execute scripts, a defensive change delivered in Microsoft’s December 2025 security updates that aims to block a high‑severity remote code execution path and force explicit, safer choices for...
Microsoft has issued KB5074204, a targeted security update for Windows PowerShell that ships as a hotpatch for devices on the 24H2 and 25H2 code families (OS Builds 26100.7456 and 26200.7456). The patch introduces a notable behavior change: the legacy PowerShell 5.1 cmdlet Invoke‑WebRequest now...
Windows PowerShell 5.1 now stops and asks for confirmation before it will parse web pages in a way that could execute scripts found in that content — a safety-first change that will affect interactive use and any automation that previously relied on the old, IE‑backed HTML DOM parsing behavior...