Google published a Stable channel update for the desktop version of Chrome on 9 November 2026 that addresses CVE‑2026‑125350, a use‑after‑free vulnerability in the browser’s XML component. The vendor classified the flaw as High severity and explicitly stated, “Google is aware that an exploit for CVE‑2026‑125350 exists in the wild.” No additional information about victim counts, attack vectors or campaign names was provided.
Update Details and Affected Versions
The Stable channel builds released on 9 November are 157.0.8103.50 for Linux, 157.0.8103.50/.51 for Windows and macOS, and the same 157.0.8103.50 version for Chrome on Android. Google’s post for Android notes that the mobile release contains the same security fixes as the corresponding desktop releases unless otherwise specified, and no exception was noted. For organizations using the Extended Stable channel, a separate update moved Windows and macOS to version 156.0.8078.96 and also listed CVE‑2026‑125350 among its High‑severity fixes.
The update package contains nine security fixes in total: seven rated High and two rated Medium. CVE‑2026‑125350 is described as a “High: Use after free in XML” issue and was reported anonymously on 6 November 2026. The same update also includes another High‑severity use‑after‑free bug, CVE‑2026‑125346, reported by Arni Hardarson of Neonix Security on 12 October 2026. Only CVE‑2026‑125350 is referenced in Google’s statement about an active exploit.
Severity Ratings and External Alerts
Google’s internal rating of High for CVE‑2026‑125350 is reinforced by an external advisory from Hong Kong Computer Emergency Response Team (HKCERT) issued on 10 November 2026. HKCERT assigned an “Extremely High Risk” label and reiterated that the vulnerability “is being exploited in the wild.” While HKCERT’s risk label is more severe, the primary source for the in‑the‑wild claim remains Google’s own wording.
Despite the vendor’s acknowledgement, the vulnerability does not yet have a public record in the CVE database; queries to the CVE Program API returned a “CVE_RECORD_DNE” response, and the National Vulnerability Database (NVD) returned zero results. Likewise, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) does not list CVE‑2026‑125350 in its Known Exploited Vulnerabilities catalog as of the 9 November 2026 release.
Mitigation Recommendations for Enterprises
Google’s advisory emphasizes that the fix is the official update and that simply downloading the patch is insufficient if the browser process remains running. Users and administrators must relaunch Chrome after the update to ensure the new binary is active. For managed environments, the recommendation is to enforce the update through Chrome or endpoint management tools, verify the exact installed version, and record the version after relaunch.
Enterprises should also verify that no policy pins a kiosk, virtual desktop infrastructure (VDI) image or third‑party build to an older version. Extended Stable customers need to move to version 156.0.8078.96 rather than remaining on earlier builds such as 156.0.8078.88. The advisory notes that ChromeOS and ChromeOS Flex were not listed as receiving a fix for this CVE in the 6 November 2026 Stable post, which referenced browser version 156.0.8078.93.
Because Google has not published technical details, exploit methods, or indicators of compromise (IOCs) for CVE‑2026‑125350, organizations cannot rely on signatures or hashes for detection. The advisory suggests that unexpected new browser processes, extensions, or outbound connections may be general investigative leads but are not definitive proof of compromise.
Supply‑Chain and Vendor Follow‑Up
Security teams are advised to query suppliers, managed service providers and any third‑party that runs Chrome in the organization. Key questions include: which Chrome channel is in use (Stable, Extended Stable, Android, ChromeOS), the exact build number installed, and whether a relaunch has been performed after patching. For Chromium‑based browsers from other vendors, teams should check the respective vendor’s advisory, as the Google posts and HKCERT bulletin do not provide patch status for those products.
Documenting the response—identifying owners, target dates for patching, and evidence of relaunch—helps close gaps in the organization’s risk posture. The advisory stresses that optional, user‑prompted updates alone are insufficient for environments where the vulnerability is known to be actively exploited.
Overall, the rapid rollout of the Stable channel update, combined with the explicit acknowledgement of an active exploit, underscores the urgency for both individual users and enterprise IT teams to verify their Chrome versions, apply the November 9 patches, and ensure the browser is fully restarted. Until additional technical details or public IOCs are released, the most reliable mitigation remains prompt patching and verification of the running binary.






Be First to Comment