Skip to content
PatchBriefing

Search PatchBriefing

Type at least two characters. Results update as you type.

Search CVEs, products, packages and article titles.

Nothing found. Identifiers such as CVE and GHSA can be searched in both languages.

Subscribe

Medium · 6.4 Browsers CVE-2026-95347 CVE-2026-95311 CVE-2026-95329 CVE-2026-95357

Google Chrome Stable Update Fixes Eight High-Severity Memory Safety Vulnerabilities

Google has released Chrome 154.0.8037.57 for desktop, fixing eight vulnerabilities rated Medium to Critical by Chromium's own severity scale, including multiple use-after-free and out-of-bounds write issues that could allow remote code execution outside the sandbox.

AI summary

Google has published a Stable Channel update for Chrome on desktop, addressing eight distinct memory-safety vulnerabilities identified through Chromium's internal security review process. The issues span several browser components, including the Updater, font handling, WebGL, GPU processing, ad filtering, the Views UI framework, Service Workers, and the ANGLE graphics layer. All eight were fixed in version 154.0.8037.57. Chromium's internal severity ratings for these issues range from Medium to Critical, and several involve use-after-free or out-of-bounds write conditions that could, in certain circumstances, allow code execution outside Chrome's sandbox.

What happened

Google released a Stable Channel update for Chrome on desktop that fixes eight separate vulnerabilities. These include use-after-free flaws in the Updater, AdFilter, Views, and ServiceWorker components; an out-of-bounds write issue in WebGL, GPU, and ANGLE; and a free-of-non-heap-memory issue in Fonts. Each was assigned its own CVE identifier (CVE-2026-95347, CVE-2026-95311, CVE-2026-95329, CVE-2026-95357, CVE-2026-95310, CVE-2026-95277, CVE-2026-95339, and CVE-2026-95331). All were resolved in the same release.

Technical cause

The vulnerabilities fall into a few memory-safety categories. Use-after-free conditions (CWE-416) affect the Updater (CVE-2026-95347), AdFilter (CVE-2026-95310), Views (CVE-2026-95277), and ServiceWorker (CVE-2026-95339) components, where memory is accessed after it has already been freed. Out-of-bounds write issues (CWE-787) affect WebGL (CVE-2026-95329), GPU (CVE-2026-95357), and ANGLE (CVE-2026-95331), where data can be written outside the bounds of an allocated buffer. A separate free-of-non-heap-memory issue (CWE-590) affects Fonts (CVE-2026-95311). In several cases the vendor description notes that exploitation would require a crafted HTML page or, for the Updater issue, crafted network traffic, and in most cases some form of user interaction or social engineering.

Why it matters

Several of these issues carry a Chromium-assigned severity of Critical (WebGL, GPU, AdFilter, ServiceWorker), meaning Google's own engineering team judged that successful exploitation could potentially allow an attacker to execute arbitrary code outside Chrome's sandbox. Others are rated High (Views) or Medium (Updater, Fonts, ANGLE). All eight affect a widely used browser and were scored by NVD with a CVSS base score of 9.6, reflecting the potential impact of a successful exploit, though most require a user to visit a crafted web page or, for the Updater flaw, be affected by a network traffic scenario.

Who is affected

Users running Google Chrome on desktop prior to version 154.0.8037.57 are affected. The vendor advisory specifically notes the Updater issue (CVE-2026-95347) affects Chrome on Mac, and the WebGL (CVE-2026-95329) and GPU (CVE-2026-95357) issues affect Chrome on Android. The remaining vulnerabilities are described generally for Google Chrome without a specific platform qualifier in the available text.

Affected versions

All eight vulnerabilities affect Google Chrome versions prior to 154.0.8037.57. No earlier affected version range was specified in the available data.

Fixes and mitigation

Google has fixed all eight vulnerabilities in Google Chrome version 154.0.8037.57, distributed through the Stable Channel update for desktop. No workarounds or mitigations other than updating were described in the available information.

Recommended action

Update Google Chrome to version 154.0.8037.57 or later as soon as possible. Chrome typically updates automatically, but users and administrators should verify the installed version via the browser's "About Chrome" menu and restart the browser to apply the update.

PatchBriefing score

6.4 / 10 · Medium

Official CVSS: 9.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Why this score

The Patchwire score of 6.4 reflects a high CVSS base score (9.6) contributing the bulk of the score, combined with a small additional contribution because the issues are remotely reachable by unauthenticated attackers and affect a very widely used product (Chrome). The score is moderated by the absence of known exploitation in the wild, no confirmed public exploit code, and no EPSS data being available. A fix is already available, which also limits the upward pressure on the score. Chromium's own per-issue severity ratings range from Medium to Critical; the CVSS 9.6 base score and Patchwire score reflect the aggregate technical severity rather than confirmed real-world exploitation.

Affected versions

≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched
≥ 154.0.8037.57
patched

Reported fixes

Google has fixed all eight vulnerabilities in Google Chrome version 154.0.8037.57, distributed through the Stable Channel update for desktop. No workarounds or mitigations other than updating were described in the available information.

How this was built

9 source records were collected, matched and used to prepare the report above.

  • Chrome Releases (Stable) vendor
  • NVD (NIST) database
  • NVD (NIST) database
  • NVD (NIST) database
  • NVD (NIST) database
  • NVD (NIST) database
Unified report
Google Chrome Stable Update Fixes Eight High-Severity Memory Safety Vulnerabilities
1 article · 9 sources cited
Revision history
  1. Published
  2. Generated
The Morning Brief

Relevant changes for the stacks you follow.

Choose your stacks, topics and optional WordPress plugins. At 07:00 CEST, matching advisories and releases from the reporting period are grouped into one email.

✓ Choose stacks and topics✓ Change preferences anytime✓ One grouped email