CVE-2026-126851 · Other
NO FIX YET · SEE WHAT TO DO
A use-after-free bug in Chrome's Accessibility component lets a remote attacker execute code inside the browser sandbox when the victim opens a crafted HTML page. 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 before 157.0.8103.78 who visits a malicious or compromised web page is exposed. Chromium-based browsers that pull in the same Accessibility code may be affected depending on their own release timing; the sources do not say. Users on the current Chrome release line are not affected.
Not affected if accessibility-disabled, chrome-up-to-date
Who cares chrome, desktop-browsers, linux, macos, windows
157.0.8103.78 or later.chrome://version to see the installed build number.157.0.8103.78 or later.Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside 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.