Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 4 min · 731 words
- Severity
- Routine
Edge Lockdown Mode kills WebGL and WebGPU to stop 60% of attacks
Microsoft's experimental Edge Lockdown Mode disables WebGL, WebGL2 and WebGPU to block an estimated 60% of privilege escalation attacks, trading site compatibility for defense.

Event log
- Microsoft estimates Lockdown Mode would have blocked about 60% of privilege escalation attacks on Edge users in the wild
- The feature disables WebGL, WebGL2 and WebGPU APIs and is available only in the Edge Canary channel via the #edge-sdsm-plus flag
- The feature builds on Edge Enhanced Security Mode (Super Duper Secure Mode), which removes JIT from the V8 pipeline
- Partner Security Group Manager Gareth Evans said the mode targets journalists, executives, security researchers and administrators
- The name and concept mirror Apple's Lockdown Mode for iOS and macOS
Microsoft says its new Edge Lockdown Mode would have blocked roughly 60% of privilege escalation attacks against Edge users in the wild. That figure comes from Microsoft's own estimates, not from independent testing. The feature is live now, but only in the Canary channel, and it works by breaking things on purpose.
The mechanism is blunt: Lockdown Mode disables the WebGL, WebGL2, and WebGPU graphics APIs in the browser. Microsoft frames this as reducing the attack surface in the GPU process, which the company describes as a privileged component handling complex graphics workloads across browser code, third-party libraries, and device drivers. Kill the APIs, and you kill the paths attackers use to escalate privileges and escape the sandbox.
Where did this feature come from?
The name is borrowed from Apple. The functionality builds on Edge's existing Enhanced Security Mode, known internally as Super Duper Secure Mode, which removes Just-In-Time compilation from the V8 processing pipeline. That earlier mode already traded site compatibility for safety. Lockdown Mode extends the same logic to graphics.
This is an optional, extreme tier of protection. Microsoft is explicit that it targets a narrow population, not the average enterprise desktop.
Partner Security Group Manager Gareth Evans said: "Lockdown Mode is designed for users who are at particular risk of being targeted in cybersecurity campaigns. This may include journalists, executives, security researchers, and administrators."
That list reads like a CIO's high-risk user inventory. Evans added a second qualifier: "Individuals whose threat model justifies accepting reduced compatibility in exchange for stronger protection. It may also apply to devices operating within highly restricted environments."
What breaks when you switch it on?
Websites that rely on the disabled APIs may not work as expected. Evans warned specifically about interactive graphics, meaning browser games and mapping applications are the most likely casualties. Any deployment plan for locked-down kiosks or executive laptops should inventory which internal and vendor sites depend on WebGL-based rendering before enforcement.
The enablement path confirms the experimental status. IT staff can test it today by:
- Switching to the Edge Canary release channel
- Enabling the
#edge-sdsm-plusflag - Restarting the browser
- Toggling on Strict mode under "Enhance your security on the web"
- Blocking WebGL graphics and WebGPU graphics
Once active, a "Lockdown Enabled" indicator appears in the address bar whenever WebGL or WebGPU is blocked on a page. That indicator is the only surfaced evidence of enforcement. No admin policy controls were announced.
Is the 60% claim credible?
The number deserves scrutiny. Microsoft attributes it to its own modeling of real-world attacks against Edge users, and no methodology, sample period, or dataset accompanied the announcement. Sixty percent of privilege escalation attacks is a large fraction, but privilege escalation is itself a subset of browser attacks, so the share of total attacks blocked is unstated and likely lower.
The current mitigations also cover only the GPU process. Microsoft plans to extend the feature in upcoming releases, which means today's Canary build is a floor, not the finished product.
Evans said: "The initial set of Lockdown Mode mitigations focus is the GPU process, a more privileged component that handles complex graphics workloads across browser code, third-party libraries, and device drivers."
He continued: "Results from this experiment will inform the finished Lockdown Mode experience, including clearer descriptions of restricted capabilities and site-level exceptions that restore trusted sites without weakening protection everywhere else."
Site-level exceptions matter for enterprises, since blanket API blocking without an allowlist mechanism would be unmanageable at scale. Those exceptions do not exist yet; Microsoft has only promised them.
What else has Microsoft hardened in Edge recently?
This is not an isolated effort. Last year Microsoft added an Edge scareware sensor so that Defender SmartScreen blocks scam pages faster. The company also restricted access to Edge's Internet Explorer mode after discovering that hackers were exploiting zero-days in the Chakra JavaScript engine to reach target devices.
The pattern is consistent: Microsoft keeps narrowing what the browser will execute, one engine or API at a time, and keeps shipping the changes as opt-in first. Lockdown Mode follows that playbook. Enterprises watching for the stable-release version should track whether site-level exceptions and group policy controls arrive before general availability, because without them the 60% figure buys compatibility problems Microsoft has already conceded will occur.
via bleepingcomputer.com (Source)
More from Daniel Okafor
Show full bio
Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.
201 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Microsoft fixes 1,235 flaws, one exploited Outlook zero-day
- SignDrop zero-day can grant Windows attackers SYSTEM privileges
- Apple splits Mac permissions as AI agents gain deeper access
- Microsoft Unveils Windows Server 2028 With Hardened Server Core Default
- Malicious PyPI versions of Microsoft's Agent Framework stole Azure and CI credentials