CVE-2026-126841 · Runtime
NO FIX YET · SEE WHAT TO DO
A flaw in Skia, Chrome's graphics library, lets an attacker who already controls the renderer process read memory outside the sandbox via a crafted HTML page. The attacker gets memory outside the sandbox, which may expose sensitive data, but the sources do not describe code execution.
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 Chrome install before 157.0.8103.78 is affected, including desktop browsers on every platform the browser runs on. Exploitation requires an attacker who has already compromised the renderer process, so a standard browser with no other compromise is less exposed, but a malicious page is the delivery path. Organisations with managed Chrome fleets should confirm all endpoints are on the fixed build.
Not affected if chrome-already-updated
Who cares browser, chrome, desktop, managed-endpoints
157.0.8103.78 are affected.google-chrome --version (Linux) or the About page on Windows and macOS.157.0.8103.78 or later.Out of bounds read in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory 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.