Security
Google patches Chrome zero-day CVE-2026-125350, a high-severity XML use-after-free exploited in the wild: fixed in 157.0.8103.50 and .51, the eighth exploited Chrome zero-day of 2026, and attack details have not been disclosed
Google fixed Chrome zero-day CVE-2026-125350, a high-severity XML use-after-free exploited in the wild, in 157.0.8103.50/.51. Update and restart the browser.
Google released Chrome 157.0.8103.50/.51 on November 9 to fix CVE-2026-125350, a high-severity use-after-free in Chrome’s XML component that Google says is exploited in the wild. The flaw was reported anonymously on November 6. Google has not said who is using it or how, so the practical advice is simple: update Chrome and restart it.
The essentials
- The flaw: Google says it is aware that an exploit for CVE-2026-125350 exists in the wild. The Hacker News describes it as a use-after-free in the XML component, a class of bug that can lead to crashes or arbitrary code execution. Ostorlab’s analysis, not Google’s wording, places it in the bundled XSLT library.
- The fix: Chrome 157.0.8103.50 or .51 for Windows and Mac and 157.0.8103.50 for Linux, per Cybersecurity News. Chrome Geek notes Android gets the same security fixes as the matching desktop release unless Google says otherwise. Rollout is gradual over days to weeks, and a restart is needed to apply it.
- The release: the update fixes nine vulnerabilities, seven rated High and two Medium, and only CVE-2026-125350 is flagged as exploited. Security sites count it as the eighth Chrome zero-day exploited in 2026.
- Timeline and status: an anonymous researcher reported it on November 6 and the patch shipped three days later. Ostorlab says it was not in the CISA Known Exploited Vulnerabilities catalog as of November 10, while an OffSeq page says no exploitation is on record; both conflict with Google’s statement and likely reflect lag.
What Google has not said
No indicators of compromise, no target profile and no attacker attribution have been published. Google usually withholds bug details until most users have updated, so claims about who is being hit are speculation.
What to do
Open the Chrome menu, check About Chrome, install the update and relaunch. Other Chromium-based browsers should be updated when their vendors ship the fix. This is general guidance, not a security audit.
What is not established
- Who is exploiting the flaw and against whom: not disclosed.
- How the exploit is delivered: Google gave no detail.
- A CVSS score: not yet assigned by NVD in the sources read.
- Whether other Chromium browsers are fixed: not covered in the sources.
Summary table
| Point | What is stated as of November 7, 2026 | Source |
|---|---|---|
| CVE | CVE-2026-125350, use-after-free in XML, High | The Hacker News |
| Fixed versions | 157.0.8103.50/.51 on Windows and Mac, .50 on Linux | Cybersecurity News |
| Reported | November 6, 2026 by an anonymous researcher | BleepingComputer |
| Count | Eighth exploited Chrome zero-day of 2026 | BleepingComputer |
| Same release | Nine fixes, seven High and two Medium | Chrome Geek |
FAQ
How do I know if I am protected?
Check chrome://settings/help; you should be on 157.0.8103.50 or later, and you need to restart the browser.
Is the flaw really exploited?
Google says it is aware that an exploit exists in the wild; it has not said how widely.
Do I need to update on Android?
Yes. Chrome 157 for Android carries the same security fixes unless Google notes otherwise.
Method and limits
Sources checked on November 10, 2026: BleepingComputer, The Hacker News, Cybersecurity News, Ostorlab and Chrome Geek, read as search extracts. Google’s Chrome release post and the NVD entry were not read directly. Not a security audit.
Sources
- BleepingComputer: Google patches eighth Chrome zero-day exploited in attacks this year (verified 2026-11-08)
- The Hacker News: Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026 (verified 2026-11-08)
- Cybersecurity News: Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely (verified 2026-11-08)
- Ostorlab: Chrome XSLT Use-After-Free Exploited in the Wild (CVE-2026-125350) (verified 2026-11-08)
- Chrome Geek: Chrome Zero-Day CVE-2026-125350: Update to 157.0.8103.50 (verified 2026-11-08)
Spotted an error in this article? Report it · Our corrections policy