CVE-2026-125347 · Runtime
NO FIX YET · SEE WHAT TO DO
A flaw in Chrome's FileSystem component lets a crafted HTML page run code outside the browser sandbox when a user is tricked into visiting it. The sources say the fix is in Chrome 157.0.8103.50 and later.
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 older than 157.0.8103.50 is exposed when they open a malicious page. Managed fleets and kiosks that pin Chrome versions are affected until updated. Users on current Chrome builds are not affected.
Not affected if chrome-157.0.8103.50-or-later
Who cares browser, chrome, desktop
google-chrome --version157.0.8103.50157.0.8103.50Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.50 allowed a remote attacker leveraging social engineering 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.