CVE-2026-125343 · Runtime
NO FIX YET · SEE WHAT TO DO
A buffer overflow in Chrome's Compositing component 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 10, 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.50 who browses untrusted web pages is exposed. Chromium-based browsers that pull the same Compositing code may also be affected, depending on their own release timing. Systems where Chrome is not used to browse external sites are less exposed.
Not affected if chrome-updated, no-untrusted-browsing
Who cares browsers, chrome, desktop
google-chrome --version157.0.8103.50157.0.8103.50 or laterBuffer overflow in Compositing in Google Chrome prior to 157.0.8103.50 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.