Google released Chrome 157.0.8103.50 on Monday 9 November with nine security fixes, one of them for CVE-2026-125350, a High-severity flaw in the browser's XML component. Google says it is aware of an exploit for that bug in the wild.
Two days later Google shipped a second Stable update with 83 more security fixes, so 157.0.8103.50 is now the minimum to accept and no longer the build to aim for.
What Google has confirmed
Google's release note describes the bug as "Use after free in XML". A use-after-free is a memory error: software frees a piece of memory and then goes on using it.
The CVE record, published by Google's Chrome team on 10 November, says the flaw affects Chrome before 157.0.8103.50 and that a remote attacker could use a crafted HTML page to run code of their choosing inside the sandbox, the browser's restricted environment for web content. The record does not describe an escape from it.
High is Google's own rating. CISA's scoring, attached to the same record, gives the flaw 8.8 on CVSS 3.1, with no privileges needed and user interaction required. In plain terms, the attack starts with someone opening a web page.
Google's note does not say who is using the exploit or against whom, and warns that bug details may stay restricted until most users have the fix.
CISA added the flaw to its Known Exploited Vulnerabilities Catalog on 10 November and set a due date of 24 November, the same listing day and deadline it gave the exploited Outlook flaw from this month's Patch Tuesday. That deadline binds US federal agencies. We read it as a measure of urgency for everyone else.
By BleepingComputer's count, this is the eighth Chrome zero-day exploited in attacks that Google has patched this year. The outlet lists the seven earlier ones by CVE.
Where the fix is, browser by browser
CISA's entry warns that the flaw could affect other browsers built on Chromium, naming Edge and Opera. By each vendor's own release notes, these are the first releases with the fix:
| Browser | First release with the fix | Released |
|---|---|---|
| Chrome for desktop | 157.0.8103.50 (Windows and Mac: .50/.51) | 9 November |
| Chrome for Android | 157.0.8103.50 | 9 November |
| Chrome Extended Stable, Windows and Mac | 156.0.8078.96 | 9 November |
| Microsoft Edge, Stable | 157.0.4341.46 | 9 November |
| Edge for Android | 157.0.4341.53 | 11 November |
| Brave | 1.99.56 | 10 November (Android 11 November) |
| Opera | Opera 140 | 10 November |
| Vivaldi for desktop | 8.3, minor update 2 | 10 November |
Google says Android releases contain the same security fixes as the matching desktop release. Brave's notes do not name the CVE, only a move to Chromium 157.0.8103.50, Google's fixed build.
Opera 140 is built on Chromium 157.0.8103.39, older than Google's fixed build, and its notes list the fix for CVE-2026-125350 separately. Vivaldi took the fix through Chromium 156.0.8078.99 from the Extended Stable line. So we would not judge a browser by the Chromium number it reports. The vendor's release note is the better test.
The build to aim for
On Wednesday 11 November Google updated Stable again, to 157.0.8103.78/.79 on Windows and Mac and 157.0.8103.78 on Linux. That note lists 83 security fixes, five rated Critical and 78 High, and flags none as exploited.
Brave 1.99.57 followed on 12 November, built on Chromium 157.0.8103.79. Edge 157.0.4341.57 arrived on 13 November with what Microsoft calls the latest Chromium security updates, and no CVE list so far.
How to check and update
On a computer, Google's help page gives the route: open the More menu at the top right, choose Help, then About Google Chrome. The version number sits under the Google Chrome heading. Chrome checks for an update while that page is open, and the Relaunch button applies it. If there is no Relaunch option, you are on the latest version.
The relaunch is the step that matters. Google says updates normally happen in the background when the browser is closed and reopened, so a browser left open since last week may still be running the old build. Open tabs and windows come back afterwards, though Incognito windows do not.
On Linux, Google says to use your package manager. On Android the update comes through Google Play. Google expects the desktop rollout to take days or weeks, which is the reason to check by hand.
If you manage a fleet, ask your inventory for version numbers. By the CVE record, Chrome builds before 157.0.8103.50 are affected. The exception is the Extended Stable channel, where Google lists the fix in 156.0.8078.96.
What we would do first
Our advice, in order:
- Relaunch every Chromium-based browser today. Then check each version against the table above.
- Aim for the newest build. For Chrome that means 157.0.8103.78/.79 or later.
- On managed machines, put a deadline on the restart. An update that has been downloaded but not applied protects nobody.
- Make it routine. Eight exploited Chrome zero-days so far this year is roughly one every six weeks. We would decide now who checks browser versions after each one, so the next fix does not wait for somebody to read the news.