CVE-2026-126917 · Other
NO FIX YET · SEE WHAT TO DO
A memory corruption bug in the V8 JavaScript engine in Google Chrome lets a remote attacker run arbitrary code inside the browser sandbox when a 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 is exposed when they open a malicious web page. Chromium-based browsers that pull in the same V8 engine may also be affected, depending on their own update timing. Systems that never run a browser are not affected.
Not affected if chrome-updated, non-chromium-browser
Who cares browser, chrome, desktop, mobile, v8
157.0.8103.78 or later.chrome://version in the address bar.157.0.8103.78 or later.Memory corruption in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially 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.