Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX news · Global

Microsoft Tests Edge Lockdown Mode to Disable GPU APIs and Reduce Attack Surface

Based on reporting from BleepingComputer

Published by the source: Thu, 19 Nov 2026 06:46:00 -0500

AEGLIX News

Microsoft is developing Edge Lockdown Mode, a new security feature designed to reduce the browser's attack surface by disabling WebGL, WebGL2, and WebGPU APIs, according to BleepingComputer. The mode is currently being tested in the Edge Canary channel and aims to stop attacks that attempt to escalate privileges and escape the sandbox. Microsoft estimates the feature would have blocked around 60 percent of privilege escalation attacks targeting Edge users in the wild.

Lockdown Mode draws inspiration from Apple's Lockdown Mode and builds upon Edge Enhanced Security Mode, internally known as Super Duper Secure Mode, which disables JIT compilation from the V8 processing pipeline. The feature offers optional extreme protections for users facing highly targeted attacks who are willing to accept reduced website compatibility for stronger defenses. Websites relying on the disabled APIs, particularly interactive graphics such as games or maps, may not function as expected when the mode is activated.

The current Canary implementation blocks websites from accessing WebGL, WebGL2, and WebGPU APIs, directly targeting a vector used for sandbox escapes and privilege escalation. This approach extends Microsoft's recent browser hardening efforts, which included introducing a scareware sensor to accelerate Defender SmartScreen blocking of scam pages and restricting access to Internet Explorer mode after hackers exploited zero-day vulnerabilities in the Chakra JavaScript engine.

Microsoft plans to extend Lockdown Mode in upcoming releases, using testing results to inform clearer descriptions of restricted capabilities and to develop site-level exceptions for improved compatibility. The company has not announced a general availability timeline for the feature.

Report prepared 2026-11-19 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.

Sources

Read original source · BleepingComputer (opens in a new tab)

Privacy policy

Explore the story

Consult the cited publisher for the original reporting, updates and supporting evidence. Check the publication date and source before acting on a headline.

These are research tools; no CVE, indicator, or campaign relationship is inferred from this article.

More from BleepingComputer

← Back to security news