Skip to content
Log inRegister
Criticalrisk levelConfirmedGCC/MENA relevance

Chrome Zero-Day CVE-2026-125350: Exploited XML Flaw Fixed in Version 157

Dr. Abeer Alshammari · Published 11/15/2026

Vulnerability Intelligence

CVE
CVE-2026-125350
CVSS
8.8
Affected product
Google Chrome for Windows, macOS and Linux (before 157.0.8103.50)
Exploit status
Actively exploited
CISA KEV listed
Yes
Patch status
Fixed in Chrome 157.0.8103.50 (Linux) and 157.0.8103.50/.51 (Windows and macOS)
CyberAbeer priorityUrgent

CyberAbeer's own prioritization guidance, based on severity, known exploitation, and exposure -- not an official vendor or CISA rating.

Sources last checked 11/15/2026

Google has fixed CVE-2026-125350, a use-after-free flaw in the XML component of Chrome, and says an exploit exists in the wild. CISA added it to the Known Exploited Vulnerabilities catalog. Update Chrome to 157.0.8103.50 or later and confirm that browsers have actually restarted.

What happened

On 10 November 2026 Google released a Chrome stable update that fixes CVE-2026-125350, a high severity use-after-free bug in the browser's XML component. Google's advisory states that it is aware an exploit for the flaw exists in the wild, but it has not said who is using it or how. The bug was reported by an anonymous researcher on 6 November. Public reporting counts it as the eighth Chrome zero-day exploited in attacks during 2026. CISA has added it to the KEV catalog with a federal remediation date of 24 November 2026.

Why it matters

Chrome is on almost every managed laptop and many personal phones, and the attack surface is simply a web page. A browser zero-day with confirmed exploitation turns ordinary browsing and link clicking into an entry point. Because Google gives no detail on the attacks, defenders should assume targeted use today and wider use as the patch is analysed.

Who is affected

Chrome on Windows, macOS and Linux before version 157.0.8103.50 (157.0.8103.50 or .51 on Windows and macOS). Other browsers built on Chromium may inherit the flaw until their vendors ship the matching fix, so check each vendor's advisory.

Technical impact

According to the CVE description, a remote attacker could execute arbitrary code inside the browser sandbox through a crafted HTML page. The published CVSS score is 8.8. Code execution inside the sandbox is normally one step in a chain: attackers then pair it with a sandbox escape or a separate privilege flaw to reach the operating system. Secondary reports disagree on whether the component is XML or V8; the CVE record and the CISA entry point to XML, which is what this article uses.

Governance impact

This is a patch SLA test for browsers, which are often treated as self-updating and therefore left out of vulnerability reporting. The KEV listing gives a clear external benchmark: exploited flaws should be closed within days, not within the normal monthly cycle. Boards and risk committees should ask whether browser version compliance is measured and reported.

What security teams should do

Push Chrome 157.0.8103.50 or later through your endpoint management tools. Chrome downloads updates in the background but only applies them after a restart, so report on running versions, not installed versions. Force a relaunch window for long-lived sessions. Track Chromium-based browsers and embedded runtimes (Edge, Electron apps) separately. Review web proxy and EDR telemetry for browser crashes and unusual child processes from the last two weeks.

What executives should know

A widely used tool is under confirmed attack and the fix is free and available now. The question for leadership is speed: how many hours it takes for the organisation's browser fleet to reach the fixed version, and who owns that number. Ask for the current compliance figure this week.

Sources: Google Chrome release notes and advisory as reported by The Hacker News and Security Affairs, and the CISA Known Exploited Vulnerabilities catalog as summarised by SecurityOnline. The CISA alert page could not be opened directly from our tools, so details were cross-checked across these secondary sources. Last checked 15 November 2026.

Back to Cyber Intelligence