Short answer: CVE-2026-125350 is a high-severity use-after-free in Chrome’s XML component that attackers were already exploiting when Google patched it on 9 November 2026. A specially crafted webpage can execute code inside the browser sandbox, with no download or email click required. The fix is the Chrome 157 update: open Menu > Help > About Google Chrome, let it download, then click Relaunch. Windows and macOS need 157.0.8103.50 or .51; Linux needs 157.0.8103.50.
What happened
On 6 November 2026, an anonymous researcher reported a use-after-free bug in Chrome’s XML handling to Google. Three days later, on 9 November, Google shipped a fix in the Stable Desktop channel and confirmed that an exploit exists in the wild.
The update covers nine vulnerabilities in total:
- Seven rated high, including the exploited XML bug, a second XML use-after-free (CVE-2026-125346), and bugs in WebGL, FileSystem, Compositing, the GPU process, and V8.
- Two rated medium, both uninitialized-resource issues in the GPU component.
Most of these were found by Google’s own security team. The exploited flaw was reported externally.
What a use-after-free means
A use-after-free (CWE-416) occurs when a program releases a block of memory but leaves a pointer referring to it. If an attacker can influence what happens next, the stale pointer can be made to reference attacker-controlled data. In a browser, the practical result is often code execution inside the renderer sandbox.
CISA’s description of CVE-2026-125350 says a remote attacker can execute arbitrary code inside the sandbox through a specially crafted webpage. That is the important detail: the delivery route is a web page. You do not need to download an attachment or click a link in an email. Visiting a page that contains the exploit may be enough.
Google has not disclosed who is being targeted, how the exploit is delivered in practice, or whether it is chained with a sandbox escape. Bug details and links remain restricted while the patch rolls out, which is standard practice for actively exploited flaws.
The public Chromium change appears to touch Chrome’s bundled copy of libxslt and a cache used during XSLT pattern matching. Google has not confirmed that reading, so treat it as analysis rather than an official root-cause statement.
How to patch Chrome
- Open Chrome.
- Click the three-dot menu in the top-right corner.
- Go to Help → About Google Chrome.
- Chrome checks for updates automatically. Let it download.
- Click Relaunch.
| Platform | Fixed version |
|---|---|
| Windows | 157.0.8103.50 or 157.0.8103.51 |
| macOS | 157.0.8103.50 or 157.0.8103.51 |
| Linux | 157.0.8103.50 |
Google says the rollout will reach all users over days or weeks. If the About page does not offer it yet, check again later. A build below 157.0.8103.50 stays exposed until it updates and relaunches.
Why the “eighth this year” matters
CVE-2026-125350 follows seven other Chrome zero-days exploited in 2026: CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046, and CVE-2026-87491. Four of the eight were in V8, the JavaScript engine. The previous one, an out-of-bounds write in V8, was patched on 9 September.
That is roughly one actively exploited browser zero-day every six weeks. The practical takeaway is that browser patching is a weekly task, not a monthly one. Automatic updates are worth enabling on every machine you own.
CISA KEV and what it means for administrators
CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 9 November 2026, with a remediation due date of 12 November 2026 for U.S. federal civilian agencies. KEV inclusion means there is confirmed evidence of active exploitation, and it turns the flaw into a prioritized remediation item.
For IT teams:
- Push Chrome 157 through your update rings now.
- Verify the installed version number, not just a compliance policy that reports “up to date.”
- Inventory other Chromium browsers in your estate.
- Chrome’s patch does not automatically fix Edge, Brave, Opera, or Vivaldi. Each vendor ships its own fix on its own schedule.
What you can do besides updating
There is no vendor-provided workaround for this flaw. Updating is the fix. In the meantime, reducing exposure to untrusted web pages is sensible: keep other software patched, avoid unnecessary browsing in privileged contexts, and use separate profiles or accounts for administrative work.
FAQ
Is CVE-2026-125350 being exploited?
Yes. Google says an exploit exists in the wild. Technical details about the attacks have not been released.
Which Chrome version fixes it?
157.0.8103.50 or .51 on Windows and macOS, and 157.0.8103.50 on Linux.
Do I need to relaunch?
Yes. The patch is not active until you relaunch the browser.
Does this affect Firefox or Safari?
This is a Chromium vulnerability. Other Chromium-based browsers may be affected and need their own vendor fixes. Firefox and Safari use different engines.
What is CISA KEV?
The Known Exploited Vulnerabilities catalog lists flaws with confirmed real-world exploitation. Inclusion signals urgent remediation.
Tools I use
🎙️ Voice-over made with ElevenLabs: https://try.elevenlabs.io/p825ulh2ac98
Some links are affiliate links; I may earn a commission at no extra cost to you.
Leave a Reply