The short version
- The flaw. CVE-2026-125350 is a high-severity use-after-free bug in Chrome's XML component. An anonymous researcher reported it to Google on 6 November, and Google says an exploit for it exists in the wild.
- The fix. The patch ships in Chrome 157.0.8103.50/.51 for Windows and macOS and 157.0.8103.50 for Linux, alongside eight other fixes. Google says the update may take days or weeks to reach every user.
- What is not known. Google has released no details of how the flaw is being exploited or who is behind the attacks. CISA has not added CVE-2026-125350 to its Known Exploited Vulnerabilities catalogue.
- The pattern. This is the eighth Chrome zero-day exploited in the wild in 2026, after seven others patched between February and September. Google also fixed eight exploited Chrome zero-days in 2025.
Timeline
| Date | Event |
|---|---|
| 6 Nov | An anonymous researcher reports the XML component flaw to Google. |
| 10 Nov | Google's Chrome 157 security update and its statement that an exploit exists in the wild are reported. Chrome 157.0.8103.50/.51 is available for Windows and macOS, and 157.0.8103.50 for Linux. |
What went wrong in the XML component
The bug is a use-after-free, a memory corruption flaw that arises when a program keeps a pointer to a memory location after freeing the object stored there. In Chrome it sits in the XML component, which parses XML data. According to BleepingComputer, the XML parser frees an object but does not clear the pointer to it, and an attacker can then use that stale reference to shape memory and run code.
Google rated the flaw high severity and assigned it CVE-2026-125350. In its advisory the company said it is "aware that an exploit for CVE-2026-125350 exists in the wild", without saying what the attacks do, whom they target or who is running them. Google added that details and links may stay restricted until most users have the fix, and longer if the bug also affects a third-party library other projects rely on.
Who is affected and how to update
The fix is in the Stable Desktop channel for Windows, macOS and Linux. The update also carries eight other patches: six high-severity flaws in the WebGL, FileSystem, Compositing, GPU, V8 and XML components, most found internally, and two medium-severity uninitialised resource issues in the GPU component.
Chrome installs updates on its own after the next launch, or a user can open More > Help > About Google Chrome and select Relaunch. BleepingComputer reported that the update was already offered when it checked. The Hacker News notes that users of other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, are also advised to apply the fixes as and when they become available.
An eighth exploited zero-day in one year
The seven earlier Chrome zero-days exploited this year were CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491. They covered an iterator invalidation bug in CSS font feature handling, out-of-bounds and type confusion flaws in the V8 JavaScript engine, a Skia graphics library out-of-bounds write and a use-after-free in the Dawn WebGPU implementation, patched between February and September.
SecurityWeek notes that CISA has not yet added the new CVE to its Known Exploited Vulnerabilities catalogue. None of the sources link this flaw to a named campaign, malware family or threat group.
What is not known yet
- Who is exploiting CVE-2026-125350 and what the attacks are designed to achieve.
- How many Chrome users or organisations have been affected, and whether any data was taken.
- Whether the flaw was used to deliver spyware, as some earlier Chrome zero-days were.
- What the reference to a third-party library in Google's advisory means in this case.
- Whether CISA will add CVE-2026-125350 to its Known Exploited Vulnerabilities catalogue.
What to do
If you use Chrome on desktop
- Open More > Help > About Google Chrome and install version 157.0.8103.50/.51 on Windows or macOS, or 157.0.8103.50 on Linux.
- Relaunch the browser so the update takes effect, and check the version again afterwards.
- Leave automatic updates on so future fixes install at the next launch.
If you run Chromium-based browsers
- Check Edge, Brave, Opera and Vivaldi for vendor updates that include the same fix and deploy them when available.
- Confirm the installed version on managed endpoints rather than assuming the browser updated itself.
For everyone else
- Track browser patch levels across the estate: eight Chrome zero-days have been exploited in 2026, so a slow update cycle leaves a recurring window of exposure.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.