Back Hwbusters Edge Lockdown Mode Cuts Off WebGL and WebGPU to Keep Attackers Out of the GPU Process
Microsoft is testing Edge Lockdown Mode in Canary, an opt-in hardening tier that blocks WebGL, WebGL2 and WebGPU so web pages can no longer reach the browser’s privileged GPU process. Microsoft says it would have stopped roughly 60% of the privilege escalation exploits seen in the wild since 2022.
Microsoft is testing Edge Lockdown Mode in Canary, an opt-in hardening tier that blocks WebGL, WebGL2 and WebGPU so web pages can no longer reach the browser’s privileged GPU process. Microsoft says it would have stopped roughly 60% of the privilege escalation exploits seen in the wild since 2022.
Microsoft has started testing Edge Lockdown Mode, a new layer on top of Edge’s Enhanced Security Mode that does something no browser vendor would ever make a default: it switches off hardware-accelerated graphics for the web. In the current Canary build, turning it on stops sites from using WebGL, WebGL2 and WebGPU entirely. The feature is laid out in a post on Microsoft’s Browser Vulnerability Research blog by Gareth Evans, Rob Franco and Karl Tang, and was picked up this morning by BleepingComputer .
The reasoning comes down to how modern browser exploits work. Attackers rarely win with one bug. A typical chain starts with code execution inside the sandboxed renderer, usually through V8 or Blink, and then needs a second flaw in something more privileged to break out. The GPU process is a tempting target for that second step. It sits above the renderer, and it drags in browser code, third-party translation layers and the graphics drivers underneath them. WebGL and WebGPU are the main doors web content uses to reach all of it.
Microsoft points to Google’s own release notes as proof that those doors get used. Chrome patched an actively exploited ANGLE and GPU bug in July 2025 and another exploited ANGLE flaw in December 2025, and high-severity bugs in Dawn, Chromium’s WebGPU implementation, keep turning up in stable updates. Take the APIs away from untrusted pages and those bugs become unreachable, whatever else is wrong with the code behind them.
Not for gamers, and not meant to be
The cost is obvious to anyone who reads this site. Browser games, 3D product configurators, maps, design tools and data visualisations break or degrade without GPU access, and in-browser AI tools built on WebGPU compute go down with them. Microsoft is upfront it and says it does not expect most Edge users to want the feature. The target audience is journalists, executives, security researchers and administrators, people whose threat model justifies a less capable browser, plus devices running in tightly restricted environments. The name is borrowed on purpose from Apple’s Lockdown Mode, which arrived with iOS 16 in 2022 and also shuts off JIT in Safari unless a site is excluded.
Per-site exceptions are part of the plan, so a trusted web app can get its GPU back without reopening the whole browser. Microsoft also flags WebNN, the machine-learning API that can lean on hardware acceleration, as part of the same attack surface, and says the full set of restrictions will take several releases to land.
For now it sits behind a flag in Edge Canary. Enable edge-sdsm-plus on the flags page, restart, then set “Enhance your security on the web” to Strict in Edge’s privacy and security settings. Two new toggles, Block WebGL graphics and Block WebGPU graphics, show up underneath. They are on by default for profiles that never used Enhanced Security Mode, while existing ESM users have to flip them by hand. Blocked pages show a “Lockdown Enabled” badge in the address bar, and DevTools logs a warning for every refused request.
Whether this ships is barely in question, since Microsoft is openly asking for testers. The more interesting part is the argument behind it. WebGPU only reached broad availability recently, sold on the promise of near-native GPU compute in a browser tab. Now a browser vendor is saying that, for the people most likely to be targeted, the safest amount of GPU the open web gets to touch is none at all.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
