Google shipped Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux on November 9, 2026. The release fixes CVE-2026-125350, a use-after-free bug in Chrome’s XML handling, and Google’s release note says an exploit for it exists in the wild. CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026.
The CVE record describes the impact: a remote attacker can execute arbitrary code inside the sandbox via a crafted HTML page. The only thing a user has to do is load that page. Chrome rolls the update out over days or weeks and applies it only after a relaunch, so a machine can have the fix downloaded and still run the vulnerable build.
CISA’s KEV entry also says the bug could affect other Chromium-based browsers, including Microsoft Edge and Opera. Microsoft’s Edge security release notes now list a fix in Edge Stable 157.0.4341.46, released November 9, 2026, and in Edge for Android 157.0.4341.53, released November 11, 2026.
CVE-2026-125350 at a glance
CVE-2026-125350
| Component | XML (Chromium), use-after-free (CWE-416) |
|---|---|
| Impact (CVE record) | Arbitrary code execution inside the sandbox via a crafted HTML page |
| Affected | Google Chrome prior to 157.0.8103.50 |
| Fixed (Windows, Mac) | 157.0.8103.50/.51 |
| Fixed (Linux) | 157.0.8103.50 |
| Severity | Chromium: High; CVSS 3.1 8.8 (CISA ADP) |
| Exploited | Yes: Google confirms an exploit in the wild; CISA KEV added Nov 10, 2026 |
| KEV due date | Nov 24, 2026 (US federal civilian agencies) |
| Microsoft Edge (desktop) | 157.0.4341.46 or later |
| Microsoft Edge (Android) | 157.0.4341.53 or later |
The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network attack, low complexity, no privileges, user interaction required. Chrome’s release note credits an anonymous reporter on November 6, 2026, and the Chromium issue (582442907) is restricted. Google hasn’t published attacker, campaign or target details, and no indicators of compromise have been released.
Update Chrome and confirm the version
On a single machine:
- Open
chrome://settings/help(Menu > Help > About Google Chrome). - Let Chrome download the update, then click Relaunch.
- Check that the version on the same page reads 157.0.8103.50 or later.
The relaunch is the step people skip. Until Chrome restarts, the old build keeps running, even if the update is already on disk.
On Linux with Google’s repository package, update through the package manager and restart the browser. These are standard package commands, not taken from Google’s advisory:
# Debian / Ubuntu
sudo apt update && sudo apt install --only-upgrade google-chrome-stable
# Fedora / RHEL
sudo dnf upgrade google-chrome-stable
# Confirm the installed version
google-chrome --version
On Windows you can read the installed version without opening the browser. This checks the file on disk, so a Chrome window that hasn’t relaunched can still be running the older build:
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
Fleet rollout: what to check
Google’s release note says the update will roll out over the coming days and weeks. For managed fleets, that staged rollout is too slow for a bug with a public exploit. Push 157.0.8103.50 or later (.50 or .51 on Windows and Mac) through your management tool, and make sure a relaunch actually happens.
CVE-2026-125350 fleet checklist
- Pull Chrome versions from your inventory or MDM and flag anything below 157.0.8103.50
- Push the update and enforce a browser relaunch, not just the download
- Re-check the running version after the relaunch window (inventory, chrome://version)
- Update Microsoft Edge to 157.0.4341.46 or later (Android 157.0.4341.53 or later) and relaunch; it is not fixed by the Chrome update
- Track Electron-based desktop apps you depend on and check each vendor's notes
- Watch the Chrome Releases blog and the KEV entry for updates
A common gap is a machine that reports the new version in inventory while the user keeps an old browser session open for days. If your management tool can report the running version or force a relaunch, use that rather than file-version checks alone.
For US federal civilian agencies, CISA’s due date for this KEV entry is November 24, 2026. For everyone else, that date is a useful outer limit, not a target.
Microsoft Edge and other Chromium browsers
CISA’s KEV entry says CVE-2026-125350 could affect multiple Chromium-based browsers, including Google Chrome, Microsoft Edge and Opera.
Microsoft’s Edge security release notes say Edge Stable 157.0.4341.46, released November 9, 2026, incorporates the Chromium security updates and contains a fix for CVE-2026-125350. Edge for Android 157.0.4341.53, released November 11, also contains the fix. As of November 13, 2026, the latest desktop Stable listed on that page is 157.0.4341.57.
Update Edge to 157.0.4341.46 or later, open edge://settings/help, and relaunch so the new version actually loads. Android users should update to 157.0.4341.53 or later from the Play Store.
- Don’t assume Opera, Brave, Vivaldi or Electron-based apps are fixed. Check each vendor’s own release notes.
- Chrome for Android 157.0.8103.78 (November 11) and Chrome for iOS 158.0.8127.35 (November 12) are later stability releases; the Chrome Releases posts for those builds do not name this CVE. Check that blog for mobile updates.
Edge ships with Windows 10 and 11, so it’s on your Windows endpoints whether or not people use it. Our Microsoft 365 security checklist for small businesses covers the wider patching routine.
Detection: what you can and can’t check
There are no published indicators of compromise for CVE-2026-125350, and Google has restricted the bug details. Realistic checks are about exposure, not compromise:
- Version check: anything below 157.0.8103.50 is in the affected range per the CVE record and NVD.
- Pending relaunch: find machines where the update downloaded but the browser hasn’t restarted. Chrome shows a pending-update indicator, and some inventory tools report the running version.
- Chromium-based browsers: inventory Edge and other Chromium browsers, since the Chrome update does not cover them. Edge’s own floor is 157.0.4341.46 (Android 157.0.4341.53).
Re-check the Chrome Releases post and the KEV entry for changes. If Google or CISA publish more details later, they will appear there first.
What to do today
Update Chrome to 157.0.8103.50 or later on every platform you manage, and force the relaunch. Then update Edge to 157.0.4341.46 or later (Android 157.0.4341.53 or later) and relaunch that too. Google confirms an exploit exists, CISA lists it as known exploited, and the attack needs nothing more than a visit to a crafted page. For broader update troubleshooting on Windows clients, see how to fix Windows Update when it gets stuck.