Chrome (Edge, Brave, Opera, Electron apps, ChromeOS) · CVE-2026-125350
Chrome zero-day
Patch nowExploited via web pages. In CISA KEV, due 24 Nov.
A use-after-free bug in Chromium's XML handling lets a crafted web page run code inside the browser's sandbox. Google says an exploit exists in the wild. It's fixed in Chrome 157.0.8103.50 (9 Nov 2026), and Edge, Brave, Opera and Electron have shipped fixes too.
How scary is it?
Are you affected? only if all are true
1An unpatched Chromium-based browsercommand
Chrome below 157.0.8103.50 on desktop and Android (Extended Stable below 156.0.8078.96; ChromeOS fixed in 156.0.8078.102). Also Edge below 157.0.4341.46 (Extended Stable 156.0.4314.80, Android 157.0.4341.53), Brave below 1.99.56 and Opera below 140.0.6074.17, and Electron apps built before Electron 45.3.0, 44.11.1 or 43.8.8. Chrome only applies updates after a relaunch.1,2,3,4,6,7,8,11,12,13
chrome://settings/help2Someone visits a malicious page
A crafted web page is enough to run code inside the browser's sandbox. Google says an exploit exists in the wild.5,10
What to do
1Update Chrome and relaunchcommand
Open the About page; Chrome checks for an update, then click Relaunch. Any 157.0.8103.50 or later build is fixed, including Chrome 158. Admins: check the version your fleet actually runs, since rollouts take days or weeks.1,2
chrome://settings/help Latest safe versions checked 20 Nov
2Check the version from a shellcommand
Linux shown. On macOS run "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --version. On Windows, use the About page or chrome://version.
google-chrome --version3Update Edge, Brave and Opera too
Edge 157.0.4341.46 (9 Nov), Extended Stable 156.0.4314.80 and Android 157.0.4341.53. Brave 1.99.56 (10 Nov, Chromium 157.0.8103.50). Opera 140.0.6074.17 (10 Nov). Later versions are fine.6,7,8
Latest safe versions checked 20 Nov
4Update Electron apps
Desktop apps built on Electron ship their own Chromium. Electron 45.3.0, 44.11.1 and 43.8.8 (10 Nov) include the fix; their notes don't name the CVE: 45.3.0 moved to a fixed Chromium, and 44.11.1 and 43.8.8 carry the libxslt fix. An app is fixed only once it ships one of these or later, so check with each vendor.11,12,13,1
Latest safe versions checked 20 Nov
This page shows you how to check. It can't tell you you're safe.
Sources (18) and changelog
- Chrome Releases: Stable fix, exploit in the wild 9 Nov
- Chrome Releases: Extended Stable 156.0.8078.96 9 Nov
- Chrome Releases: Android 157.0.8103.50 9 Nov
- Chrome Releases: ChromeOS 156.0.8078.102 13 Nov
- CISA KEV catalog: added 10 Nov, due 24 Nov
- Microsoft: Edge security release notes
- Brave: 1.99.56 on Chromium 157.0.8103.50 10 Nov
- Opera: changelog for 140, CVE cherry-pick 10 Nov
- Electron: releases and bundled Chromium
- CVE record: code execution inside the sandbox
- Electron 45.3.0: moves to Chromium 156.0.8078.96, which has the fix
- Electron 44.11.1: libxslt use-after-free fix
- Electron 43.8.8: libxslt use-after-free fix
- Chrome Releases: ChromeOS 158.0.8127.65 lists the CVE 18 Nov
- Chrome Releases: Stable 157.0.8103.78 11 Nov
- Chrome Releases: Stable 158.0.8127.36 17 Nov
- Chrome Releases: Extended Stable 156.0.8078.108 17 Nov
- Brave: releases
- Electron sources corrected. ChromeOS 158 confirmed fixed. Safe versions added.
- Review: Electron's 10 Nov fix added (it was listed as unknown); more Edge builds; sandbox claim now cites CISA and the CVE record.
- ChromeOS fix out (156.0.8078.102).
- Added to CISA KEV, due 24 Nov. Edge, Brave and Opera fixes out.
- Published.