Microsoft Tests Edge Lockdown Mode to Disable WebGL and WebGPU

Summary
Microsoft is testing an optional Edge Lockdown Mode that blocks WebGL, WebGL2, and WebGPU to reduce risks from GPU-process attacks. It may break some sites; Microsoft estimates it could have blocked about 60% of in-the-wild privilege-escalation attacks targeting Edge.
Key points
- The experimental feature blocks websites from using WebGL, WebGL2, and WebGPU, targeting attacks that attempt privilege escalation and sandbox escape through the GPU process.
- Microsoft says the optional mode is intended for people at elevated risk of targeted attacks, including journalists, executives, security researchers, and administrators.
- Blocking graphics APIs may impair websites that rely on them, including interactive games and maps.
- Users can test the feature in Edge Canary by enabling the #edge-sdsm-plus flag and configuring Strict mode to block WebGL and WebGPU graphics.
- Microsoft plans to use experiment results to shape the finished feature, including clearer explanations and possible site-level exceptions.
- Microsoft estimates the feature would have blocked around 60% of privilege-escalation attacks targeting Edge users in the wild; this is a company estimate, not an independently verified test result.
Article Details
- Event Type
- Microsoft is testing an optional Edge Lockdown Mode that blocks WebGL, WebGL2, and WebGPU to reduce the browser’s attack surface.
- Impact
- The feature is intended to help prevent privilege-escalation attacks and sandbox escapes involving the GPU process. Microsoft estimates it could have blocked around 60% of privilege-escalation attacks targeting Edge users in the wild. Blocking these APIs may reduce compatibility for websites that rely on interactive graphics.
