Chrome 158 patches 204 flaws, including six critical memory bugs
Original title: Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws
Fixed builds are 158.0.8127.36 on Linux and 158.0.8127.36 or .37 on Windows and macOS, with no exploitation flagged.
Google began rolling out Chrome 158 for Windows, macOS, and Linux on November 17, 2026, with 204 security fixes. Six critical memory bugs in WebView, garbage collection, WebAudio, GPU, ANGLE, and Media could lead to code execution inside the browser process. The notes do not say whether any flaw was used in attacks or can escape the sandbox. Unlike a separate November zero-day notice, this announcement does not flag active exploitation.
Unconfirmed: Google did not say whether the six critical flaws were exploited or can escape the sandbox.
- Use-after-free bugs are CVE-2026-130963, CVE-2026-131008, and CVE-2026-130975.
- GPU, ANGLE, and Media bugs are CVE-2026-131031, CVE-2026-131054, and CVE-2026-131060.
- Google credited Claude with assisting the GPU and Media reports.
- Arni Hardarson received $4,000 for high-severity CVE-2026-130910.
- The downloaded update takes effect only after Chrome is restarted.
Impact: Code execution inside the affected browser process
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | — | 158.0.8127.36 for Linux; 158.0.8127.36 or 158.0.8127.37 for Windows and macOS |
- 1.Install Chrome 158 and relaunch so the patched build is in use.
- 2.Check managed fleets for devices that downloaded the update but have not restarted.
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-130910 | Sandbox escape in ANGLE in Chrome on Android before 158.0.8127.36 | 9.6 group max | — | ||
| CVE-2026-130963 | Use-after-free in Chrome Android WebView before 158.0.8127.36 | — | — |
From the original article
3 min read at cybersecuritynews.com
Google began rolling out Chrome 158 to Windows, macOS, and Linux on November 17, 2026, with 204 security fixes. The desktop release notes list six critical memory bugs that could lead to code execution. However, Google did not spell out the impact of each flaw.
By Abinaya · cybersecuritynews.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.