On this page · 9 sections
  1. Stable 157.0.8103.50/.51: XML Use-After-Free Flagged as Exploited
  2. Extended Stable 156.0.8078.96: Eleven Fixes, Four Shared With Stable
  3. WebGL, Compositing and GPU Fixes: Rendering Paths
  4. V8 Type Confusion and FileSystem Authorization Fixes
  5. CVE Identifiers and the Change Each One Belongs To
  6. Affected and Fixed Versions by Channel
  7. Update Steps for Stable and Extended Stable Users
  8. How to Confirm Your Chrome Build Has the XML and GPU Fixes
  9. Sources

Warning

Chrome Stable 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux fixes nine security issues, seven rated High and two Medium, according to Chrome Releases. CVE-2026-125350, a use after free in XML rated High, is the fix for which Google is aware that an exploit exists in the wild.

Stable 157.0.8103.50/.51: XML Use-After-Free Flagged as Exploited #

Two of the nine Stable fixes are use-after-free bugs in XML. CVE-2026-125350 (bug 582442907) was reported by an anonymous reporter on 2026-11-06. CVE-2026-125346 (bug 572578603) was reported by Arni Hardarson (Neonix Security) on 2026-10-12. Both are rated High in the Stable notes.

The in-the-wild statement is attached to CVE-2026-125350 alone, and the Stable post states it directly:

Google is aware that an exploit for CVE-2026-125350 exists in the wild.

For Stable users on Windows, Mac and Linux, this is the fact to act on first. The same notes say the update will roll out over the coming days/weeks, so an installed build may not receive the fix immediately after the release is published.

Extended Stable 156.0.8078.96: Eleven Fixes, Four Shared With Stable #

The Extended Stable channel was updated to 156.0.8078.96 for Windows and Mac, and its post lists 11 security fixes, ten rated High and one Medium, in the Extended Stable post. Four of those CVEs also appear in the Stable list with the same bug numbers: CVE-2026-125345, CVE-2026-125346, CVE-2026-125347 and CVE-2026-125350. Both posts carry the publication date 2026-11-09.

The Extended post has no in-the-wild note. The exploit statement appears only in the Stable post, so Extended Stable users should not read it as applying to 156.0.8078.96 unless that channel's notes say so. The other seven Extended items are CVE-2026-121068, CVE-2026-121076, CVE-2026-121095, CVE-2026-121208, CVE-2026-121213 and CVE-2026-121233, all High, and CVE-2026-121184, rated Medium.

WebGL, Compositing and GPU Fixes: Rendering Paths #

Three High-rated Stable fixes sit in the rendering stack. CVE-2026-125345 is an uninitialized resource in WebGL (bug 550525698, reported by Google on 2026-08-21). CVE-2026-125343 is a buffer overflow in Compositing (bug 561998123, reported by Google on 2026-09-15). CVE-2026-125348 is an out-of-bounds write in GPU (bug 563358700, reported by Google on 2026-09-18).

The two Medium-rated fixes are uninitialized resources in GPU: CVE-2026-125349 (bug 536663516, reported by Google on 2026-07-20) and CVE-2026-125342 (bug 566384898, reported by Vo Duc Thang (ugvxb) on 2026-09-26). This suggests that pages and applications using WebGL or GPU-accelerated compositing are the exposed group, since the notes name the components but not the triggers.

V8 Type Confusion and FileSystem Authorization Fixes #

CVE-2026-125344 is a type confusion in V8, rated High, reported by Google on 2026-10-02 (bug 568893995). CVE-2026-125347 is an incorrect authorization in FileSystem, rated High, reported by Google on 2026-09-15 (bug 561996724). CVE-2026-125347 is also listed in the Extended Stable post.

V8 runs the scripts of web pages, so this suggests that the type confusion fix matters to any browsing session, not only to a specific feature. The Stable notes do not tie the V8 bug to a feature, which is why this group is treated here as general browsing exposure.

CVE Identifiers and the Change Each One Belongs To #

CVEChangeComponentSeverity (per notes)ReportedBug
CVE-2026-125350Use after freeXMLHigh2026-11-06, anonymous582442907
CVE-2026-125346Use after freeXMLHigh2026-10-12, Arni Hardarson (Neonix Security)572578603
CVE-2026-125345Uninitialized resourceWebGLHigh2026-08-21, Google550525698
CVE-2026-125343Buffer overflowCompositingHigh2026-09-15, Google561998123
CVE-2026-125348Out of bounds writeGPUHigh2026-09-18, Google563358700
CVE-2026-125344Type confusionV8High2026-10-02, Google568893995
CVE-2026-125347Incorrect authorizationFileSystemHigh2026-09-15, Google561996724
CVE-2026-125349Uninitialized resourceGPUMedium2026-07-20, Google536663516
CVE-2026-125342Uninitialized resourceGPUMedium2026-09-26, Vo Duc Thang (ugvxb)566384898

Affected and Fixed Versions by Channel #

ChannelPlatformFixed versionSecurity fixes in notesAffected range
StableWindows, Mac157.0.8103.50/.519Not given in the sources
StableLinux157.0.8103.509Not given in the sources
Extended StableWindows, Mac156.0.8078.9611Not given in the sources

Both Stable rows describe the same nine fixes, and the Stable notes do not split the count by platform. The Stable Linux build is listed at 157.0.8103.50 without the .51 suffix that the Windows and Mac entry carries.

Update Steps for Stable and Extended Stable Users #

  1. On Windows or Mac, update the Stable channel to 157.0.8103.50/.51, as listed in the Chrome Releases Stable post.
  2. On Linux, update the Stable channel to 157.0.8103.50.
  3. If you run Extended Stable on Windows or Mac, update to 156.0.8078.96, as listed in the Extended Stable post.

How to Confirm Your Chrome Build Has the XML and GPU Fixes #

Compare the installed Chrome version string with the fixed versions in the table above. A Stable install on Windows or Mac should read 157.0.8103.50 or 157.0.8103.51, a Stable install on Linux should read 157.0.8103.50, and an Extended Stable install on Windows or Mac should read 156.0.8078.96. Access to bug details may be kept restricted until most users are updated, so this version comparison is the check the notes support.

Sources

  1. Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com · Nov 9, 2026
  2. Chrome Releases: Extended Stable Update for Desktop chromereleases.googleblog.com · Nov 9, 2026

Next reading

Edited and approved by Jarosław Krzemiński. Spotted a mistake? Report a correction or read the corrections policy.