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
153.0.8010.47
RELEASE SECURITY Browsers Google Chrome · released September 15, 2026 · covered September 15, 2026

Google Chrome 153.0.8010.47 Fixes 42 Security Vulnerabilities, Including Two Critical Flaws

Chrome's Stable channel has moved to 153.0.8010.47/.48, patching 42 security issues including two critical vulnerabilities in WebGL and the browser's internals.

42 security fixes 2 Critical CVEs WebGL out-of-bounds read Use-after-free in Internals
AI summary

Google has released Chrome 153.0.8010.47/.48 for Windows and Mac, and 153.0.8010.47 for Linux, to the Stable channel. The rollout happens gradually over the coming days and weeks. This update is notable for carrying a large batch of 42 security fixes, including two issues rated Critical, making it a priority update for anyone running Chrome or a Chromium-based browser.

What's in this release

This build addresses 42 security fixes in total. Google has disclosed details for two Critical-severity vulnerabilities so far: CVE-2026-91726, an out-of-bounds read in WebGL reported internally by Google on 2026-09-03, and CVE-2026-91721, a use-after-free in Chrome's Internals component reported by external researcher xinyang on 2026-09-04. As is standard practice, Google is keeping access to full bug details and links restricted for some of the fixes until most users have updated, and for any issues that trace back to third-party libraries shared with other projects that haven't yet shipped their own fixes. The complete list of changes in this build is published in the Chromium source log, and further security-specific details are tracked on the Chrome Security Page.

Why it matters for your stack

Critical-rated vulnerabilities in a browser engine can potentially be exploited through malicious or compromised web content, so a release with two Critical fixes deserves prompt attention regardless of whether an active exploit has been observed. WebGL and core browser internals are both high-value attack surfaces because they're reachable simply by visiting a page, which is why issues in these areas are typically patched quickly and with limited public detail until adoption is widespread.

How to update

Chrome generally updates itself automatically; you can confirm you're on the latest build by opening Settings > About Chrome, which also triggers a check and restart prompt if an update is pending. On managed fleets or enterprise deployments, administrators should verify that the update has been pushed through their update management tooling, since the Windows/Mac/Linux builds are rolling out progressively rather than all at once. Users of other Chromium-based browsers (such as Edge, Brave, or Opera) should also watch for a corresponding update, as these browsers typically incorporate the same underlying Chromium security fixes shortly after Google's release.

Synthesized by AI from 1 source · updated 2 hours ago
Sources · merged by AI 1 total
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