The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

Edge Lockdown Mode blocks WebGL and WebGPU

By The Daily Byte ·21 Nov 2026 ·4 min read
A person typing on a laptop displaying a website in a browser

Microsoft is testing a new Lockdown Mode for its Edge browser that switches off WebGL, WebGL2 and WebGPU, so that websites can no longer reach the browser's privileged graphics process. The feature was set out on 13 November on Microsoft's Browser Vulnerability Research blog, and is now available to try in Edge Canary, the browser's earliest test channel, behind a settings flag. It was picked up by BleepingComputer and covered by SC Media on 20 November.

Lockdown Mode builds on Edge's existing Enhanced Security Mode, which lets users switch off the V8 JavaScript engine's just-in-time compiler, the part of the browser most often attacked. Enhanced Security Mode began as an experiment in August 2021, under the internal name Super Duper Secure Mode, and reached general availability in Edge 98 in February 2022. Lockdown Mode takes the idea further: instead of only removing the just-in-time compiler, it removes whole graphics interfaces from what a website can reach.

Why the graphics process is the target

Sophisticated browser attacks usually rely on a chain of flaws. An attacker first gains code execution in the renderer, the part of the browser that draws web pages, through a vulnerability in a component such as V8 or Blink. Then they need a second flaw in a more privileged process, such as the operating system kernel or the GPU process, to escape the browser's sandbox. With those privileges, they can compromise the device, steal data, or deploy malware such as ransomware. Breaking any link in that chain can stop the whole attack.

The GPU process is a natural link to break. It is a privileged component handling complex graphics work across browser code, third-party libraries and device drivers, and web content reaches it mainly through WebGL and WebGPU. Their implementation complexity has repeatedly been exploited: Google confirmed exploitation of an ANGLE and GPU vulnerability in July 2025 and another ANGLE vulnerability in December 2025, and Chromium security updates continue to fix high-severity flaws in Dawn and WebGPU. If a website cannot call these interfaces at all, an attacker cannot exploit the code behind them.

What Microsoft says it would have stopped

Microsoft says its analysis of known exploited vulnerabilities since February 2022 shows that the current Canary version of Lockdown Mode would have mitigated roughly 60 percent of the privilege-escalation exploits observed in the wild. That is Microsoft's own retrospective estimate, not an independent test, and it covers privilege-escalation exploits only; it is not a claim that 60 percent of all browser attacks would be blocked. For comparison, Microsoft says customers who enabled Enhanced Security Mode were safe from 55 percent of the known exploited Chromium vulnerabilities over the same period.

The name is borrowed deliberately from Apple, which announced its own Lockdown Mode in July 2022 and shipped it with iOS 16 that September. Like Apple's version, Edge's mode is an optional, extreme protection for people facing highly targeted attacks, not a default for everyone.

Who it is for, and what breaks

Microsoft names journalists, executives, security researchers and administrators as the intended audience, along with devices running in highly restricted environments. Those are people whose threat model justifies trading website compatibility for stronger protection. The trade-off is real: games, design tools, maps, visualisations and other graphics-heavy sites may fail or lose functionality when their graphics interfaces are unavailable, and some will need a manual bypass. Microsoft says it does not expect most Edge users to want the feature.

WebNN, another hardware-accelerated interface for machine-learning work, is part of the same attack surface, but it is not on the current block list. Microsoft says the full set of restrictions will take several releases to land, and that Canary results will shape the finished version, including site-level exceptions for trusted sites. No date has been given for leaving Canary.

How to try it

To test Lockdown Mode, update Edge Canary, then enable the edge-sdsm-plus flag and restart the browser. Next, open the privacy and security settings, turn on Enhance your security on the web, and choose Strict. Two new toggles appear underneath: Block WebGL graphics and Block WebGPU graphics. They are switched on by default for profiles that have never used Enhanced Security Mode; existing Enhanced Security Mode users have to switch them on by hand. A Lockdown Enabled indicator appears in the address bar when WebGL or WebGPU is blocked on a page, and the developer tools console logs a warning for each blocked request. Blocking decisions can be reviewed on the security diagnostics page. Microsoft is asking testers to send feedback through Settings, Help and Support, and to mention Lockdown Mode in the report.

Source
Microsoft Browser Vulnerability Research — https://microsoftedge.github.io/edgevr/posts/Lockdown-Mode/