CVE-2026-126877 · Other
NO FIX YET · SEE WHAT TO DO
A use-after-free bug in Dawn, Chrome's WebGPU graphics component, lets an attacker who has already compromised the renderer process run code outside the browser sandbox. The attack is triggered by a crafted HTML page, and Chromium rates it High severity.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Google Chrome older than 157.0.8103.78 is exposed, and a visit to a malicious page is the entry point. The attacker must first compromise the renderer process, so this is a second-stage flaw rather than a standalone one-click takeover. Machines already on the fixed version or using a browser that does not ship this Dawn code are not affected.
Not affected if chrome-at-or-above-157.0.8103.78, no-chrome-installed
Who cares browsers, chrome, desktop, endpoints
chrome://settings/help in the browser) and compare it with 157.0.8103.78.157.0.8103.78 or later.Use after free in Dawn in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.