Chrome patches an exploited XML use-after-free (CVE-2026-125350)
Google patched CVE-2026-125350, a use-after-free in Chrome's XML component that CISA reports is known to be exploited, with fixes in 157.0.8103.50 and 157.0.8103.51.
Google has released Chrome updates that patch CVE-2026-125350, a use-after-free vulnerability in the browser’s XML component. A use-after-free is a memory-safety bug in which a program keeps using memory after it has been freed, and the CVE record classifies this one as CWE-416. The record gives the flaw a CVSS (Common Vulnerability Scoring System) v3.1 base score of 8.8, rated High.
What is affected
Chrome versions prior to 157.0.8103.50 are affected by CVE-2026-125350. According to The Hacker News, Google released updates that patch nine vulnerabilities, including one that has come under active exploitation in the wild. According to the report, the fix is included in Chrome 157.0.8103.50 for Linux. According to BleepingComputer, the Windows and macOS fix is Chrome 157.0.8103.51.
Why it matters
The US Cybersecurity and Infrastructure Security Agency (CISA) reports that CVE-2026-125350 is known to be exploited. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026, with a remediation due date of November 24, 2026. According to BleepingComputer, Google said it is aware that an exploit for CVE-2026-125350 exists in the wild. According to The Hacker News, Google has now addressed eight actively exploited Chrome zero-days since the start of the year.
CISA notes that the vulnerability could affect multiple Chromium-based browsers, including Google Chrome, Microsoft Edge and Opera. According to The Hacker News, an anonymous security researcher reported the flaw to Google on November 6, 2026.
What to do
Update Chrome to the fixed version for your platform: 157.0.8103.50 on Linux, and 157.0.8103.51 on Windows and macOS. CISA requires applying mitigations in accordance with vendor instructions. Teams that manage browser fleets should confirm the reported version on each platform rather than assuming an automatic update has landed.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .