---
title: "Microsoft Edge Lockdown Mode Blocks WebGL and WebGPU for At-Risk Users"
date: 2026-11-19
author: "Sofia Ramirez"
featured_image: "https://sqmagazine.co.uk/wp-content/uploads/2026/11/microsoft-edge-lockdown-mode-gpu-disable.jpg"
categories:
  - name: "Cybersecurity"
    url: "/cybersecurity.md"
tags:
  - name: "News"
    url: "/tag/news.md"
---

# Microsoft Edge Lockdown Mode Blocks WebGL and WebGPU for At-Risk Users

Microsoft announced Edge Lockdown Mode on 13th November, 2026, a Canary-channel test that blocks websites from using the WebGL, WebGL2, and WebGPU graphics APIs. The company’s own analysis says the build would have mitigated roughly 60% of in-the-wild privilege escalation exploits since February 2022.

## What Happened?

- Edge Lockdown Mode blocks WebGL, WebGL2, and WebGPU in Canary, with more capabilities planned over the coming releases.
- Enhanced Security Mode, the feature underneath, kept users who enabled it safe from 55% of known exploited Chromium vulnerabilities over the same period.
- Microsoft designed the mode for people at particular risk of targeting, such as journalists, executives, security researchers, and administrators.
- Existing Enhanced Security Mode users currently have to enable the GPU block settings, since Edge defaults them on only for profiles new to it.

## Edge cuts web pages off from the GPU stack

**Gareth Evans**, a Partner Security Group Manager at Microsoft, set out the plan in an [Edge blog post](https://microsoftedge.github.io/edgevr/posts/Lockdown-Mode/). Lockdown Mode extends Enhanced Security Mode, which has let users switch off V8’s just-in-time (JIT) compiler since Edge 98.

The new mode reaches deeper, starting with the GPU process. That more privileged component handles complex graphics work across browser code, third-party libraries, and device drivers. Web content reaches that stack mainly through WebGL and WebGPU, so blocking those APIs keeps the code behind them away from hostile pages.

Edge has fenced off risky code before: last year, Microsoft [restricted Internet Explorer mode](https://sqmagazine.co.uk/edge-ie-mode-zero-day-lockdown/) after attackers exploited zero-days in the Chakra JavaScript engine.

To try it in Canary:

- **Update Canary at edge://settings/help.**
- **Set edge://flags/#edge-sdsm-plus to Enabled and restart.**
- **Open edge://settings/privacy/security, turn on “Enhance your security on the web” and choose Strict.**
- **Check that Block WebGL graphics and Block WebGPU graphics are both on.**

A “**Lockdown Enabled**” badge then appears in the address bar whenever Edge blocks WebGL or WebGPU on a page. DevTools console warnings name each blocked request.

## Microsoft is aiming at the sandbox escape

Sophisticated browser attacks often rely on an exploit chain. An attacker first gains code execution in the renderer through a bug in V8 or Blink. A second bug, in the operating system kernel or a privileged process such as the GPU process, then lets the attacker escape the sandbox.

Disabling the JIT compiler works on the first link, inside V8, while Lockdown Mode goes after the second. That’s why the **55%** figure and the 60% estimate measure different things. The first covers all known exploited Chromium vulnerabilities; the second counts only privilege escalation exploits. Both are Microsoft’s own numbers, and the post doesn’t say how far the two sets overlap.

The code behind these APIs has been exploited repeatedly. Google confirmed exploitation of an ANGLE and GPU bug in July 2025 and of [another ANGLE bug in December 2025](https://sqmagazine.co.uk/chrome-zero-day-patch-december-2025/). Chromium updates still fix high-severity bugs in Dawn and WebGPU.

An earlier Evans post argued AI is changing exploit economics, citing attackers who weaponize known bugs disclosed in Chromium’s open-source code. A known bug stays exposed until its fix reaches users, so he wrote that “**faster updates alone cannot eliminate every opportunity for exploitation.**“

## Lockdown trades games and maps for a smaller target

Apple coined the name, and its Lockdown Mode also restricts JIT compilation in web browsing unless a user excludes a trusted site. Edge’s version pushes past JIT into the graphics stack, and [Microsoft](https://sqmagazine.co.uk/microsoft-statistics/) is plain about the cost. Games, design tools, maps, and visualizations may fail or lose features.

Microsoft doesn’t expect most Edge users to want that trade, which makes site exceptions the piece to watch. Canary results will shape site-level exceptions that restore trusted pages without weakening protection elsewhere, the company said. High-risk users who can’t run Canary can turn on Enhanced Security Mode in Strict, along with Update on Idle, Microsoft’s new security-update feature.

Two gaps remain. Microsoft hasn’t dated Lockdown Mode’s exit from **Canary**, and **WebNN**, another hardware-accelerated path the post names, isn’t on the current block list.

Testers who hit a broken site should report it through Settings, Help and Support, naming Lockdown Mode and the affected site. Microsoft plans to extend the mode to more capabilities over the coming releases.