CVE-2026-126883 · Other
NO FIX YET · SEE WHAT TO DO
A use-after-free bug in Chrome's Core component on Windows lets an attacker who already controls the renderer process run arbitrary code outside the browser sandbox. The attacker delivers the trigger through a crafted HTML page.
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.
Any Windows machine running Chrome older than 157.0.8103.78 is exposed when a user visits a malicious page. Exploitation requires a separate renderer compromise first, so the risk is chained. Managed fleets should confirm the deployed Chrome version.
Not affected if chrome-updated, non-windows
Who cares browser, chrome, windows
chrome://version in the address bar157.0.8103.78157.0.8103.78 or laterUse after free in Core in Google Chrome on on Windows 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.