TL;DR
Google promoted Chrome 158 to the stable desktop channel with 204 security patches for Windows, Mac, and Linux. Notably, Chrome 158 Fixes six critical memory bugs that let remote attackers run code or crash the browser. Users and admins should update to version 158.0.8127.36 or 158.0.8127.37 right away.
- Total: 7 CVEs
- Severity: 3 Critical · 3 High · 1 Unrated
- Actively exploited: None confirmed
- Highest severity: 9.6 (Critical · CVSSv3) — CVE-2026-131031
- Action: Apply the latest security updates now
Notable CVEs
| CVE | CVSS (CVSSv3) | Type | Fixed in | Status |
|---|---|---|---|---|
| CVE-2026-131031 | 9.6 | CWE-787 | 158.0.8127.36 | Not exploited |
| CVE-2026-131054 | 9.6 | CWE-787 | 158.0.8127.36 | Not exploited |
| CVE-2026-130910 | 9.6 | CWE-693 | 158.0.8127.36 | Not exploited |
| CVE-2026-131060 | 8.8 | CWE-122 | 158.0.8127.36 | Not exploited |
| CVE-2026-131008 | 8.8 | CWE-416 | 158.0.8127.36 | Not exploited |
| CVE-2026-130975 | 8.8 | CWE-416 | 158.0.8127.36 | Not exploited |
| CVE-2026-130963 | Awaiting analysis | CWE-416 | 158.0.8127.36 | Not exploited |
Why It Matters
Web browsers act as the main work tool for office staff and home users alike. Therefore, memory flaws in core browser engines pose a high risk to PC safety. In its Chrome 158 release post, Google shared details on 198 external and internal bug reports. Specifically, the list contains six Critical flaws, 62 High bugs, 78 Medium issues, and 52 Low flaws.
Furthermore, Anthropic researcher Xinyang Ge found four of the six critical flaws, often with help from the Claude AI model. Meanwhile, outside researchers earned at least $11,000 in bug bounties so far, with many rewards still pending. Neither Google nor outside teams have confirmed live attacks in the wild or public exploit code yet.
How the Attack Works
Critical Use-After-Free Flaws
First, Chrome 158 Fixes three critical use-after-free (UAF) bugs in core browser parts. These include CVE-2026-130963 in WebView, CVE-2026-131008 in GarbageCollection, and CVE-2026-130975 in WebAudio. A UAF bug occurs when the app keeps using a memory slot after freeing the old data object. As a result, a bad web page can slip rogue code into that slot and hijack the process.
Out-of-Bounds Writes and Buffer Overflows
Second, the update patches two critical out-of-bounds write bugs. CVE-2026-131031 hits the GPU engine, while CVE-2026-131054 impacts the ANGLE graphics layer. Next, CVE-2026-131060 triggers a critical buffer overflow in the Media engine. Also, Arni Hardarson at Neonix Security won $4,000 for finding CVE-2026-130910, a high-risk defense failure in ANGLE. In each case, crafted media or graphics inputs push data past safe memory limits and corrupt nearby code.
Affected Versions
Vulnerable Chrome Desktop Builds
All Chrome builds older than 158.0.8127.36 on Linux face risk. Similarly, Windows and Mac builds before 158.0.8127.36 or 158.0.8127.37 are affected.
Patch and Mitigation Steps
Google is rolling out Chrome 158 Fixes to desktop hosts over the coming days and weeks. However, users do not need to wait for an auto update. Instead, open the Chrome menu, click Help, and choose About Google Chrome to grab build 158.0.8127.36 or 158.0.8127.37 now. Finally, restart the browser to apply all patches and keep web sessions safe.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!