CVE-2026-126919 · Other
NO FIX YET · SEE WHAT TO DO
A memory-handling bug in the BrowserTag component of Google Chrome lets a crafted HTML page make the browser run code. The sources say the code runs inside the browser sandbox, not outside it.
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 version 157.0.8103.78 who opens a malicious or compromised web page. Users on current Chrome builds are not affected.
Not affected if chrome-up-to-date
Who cares browsers, chrome, desktop
chrome://settings/help, and read the version; unknown whether this is affected unless it is below 157.0.8103.78157.0.8103.78 or laterUse after free in BrowserTag 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.