Cybersecurity

Chrome 158 Security Update: 204 Fixes, Including 6 Critical Flaws

Published By Shivam Sharma7 min read
Google Chrome 158 security update fixes 204 vulnerabilities including six critical flaws

Google released Chrome 158 for Windows, Mac and Linux on Tuesday 17 November 2026, patching 204 security flaws, six of them critical. The Chrome 158 security update is rolling out over the coming days and weeks, and the patched builds are 158.0.8127.36 for Linux and 158.0.8127.36 or 158.0.8127.37 for Windows and macOS, according to Google’s Chrome Releases notice.

Google has not reported active exploitation of any of the 204 flaws. The advisory does not say any of them is being exploited in the wild, and access to individual bug details and links may remain restricted until a majority of users are updated. The striking detail is who found the worst bugs: a single outside researcher reported four of the six critical flaws, and two of those were found with help from an AI model.

One researcher found four of the six worst flaws

Xinyang Ge of Anthropic reported four of the six critical flaws in Chrome 158, and two of those four are credited as found with assistance from Anthropic’s Claude AI model, according to GBHackers. The two Claude-assisted finds are CVE-2026-131031, an out-of-bounds write in the GPU, and CVE-2026-131060, a buffer overflow in Media. Ge’s other two critical finds are CVE-2026-131008, a use-after-free in GarbageCollection, and CVE-2026-130975, a use-after-free in WebAudio.

All six critical flaws are memory-safety bugs. The other two are CVE-2026-130963, a use-after-free in WebView reported by Google on 15 September, and CVE-2026-131054, an out-of-bounds write in ANGLE reported by Google on 22 October. The table below lists them in the order they were reported.

CVE Type Component Reported by Reported
CVE-2026-130963 Use-after-free WebView Google 15 Sep 2026
CVE-2026-131031 Out-of-bounds write GPU Xinyang Ge (Anthropic, with Claude) 7 Oct 2026
CVE-2026-131060 Buffer overflow Media Xinyang Ge (Anthropic, with Claude) 13 Oct 2026
CVE-2026-131008 Use-after-free GarbageCollection Xinyang Ge 17 Oct 2026
CVE-2026-131054 Out-of-bounds write ANGLE Google 22 Oct 2026
CVE-2026-130975 Use-after-free WebAudio Xinyang Ge (Anthropic) 26 Oct 2026

The concentration is the story. Google’s own researchers discovered 145 of the 204 flaws, or 71.1 percent, while Ge discovered 15, or 7.4 percent, by TechReview’s calculation from SecurityWeek‘s discovery counts. But Ge found four of the six critical flaws, or 66.7 percent, so the outside researcher found a small share of the total and two-thirds of the worst bugs. Four of the six critical flaws sit in the graphics and media stack, the GPU and ANGLE on the graphics side and Media and WebAudio on the media side, a similar concentration to the Chrome 157 launch, where four of seven critical flaws were in the graphics and GPU stack (Dawn twice, ANGLE and WebGL).

The Claude connection is the detail that will get the most attention. Two of the six critical flaws are credited as found with assistance from Anthropic’s Claude AI model, and Google’s credit lines say so explicitly, without explaining how the AI tool was used. An AI system helping surface two of the worst bugs in Chrome is a striking detail, and it suggests AI-assisted security research is now finding the flaws that matter most, not just the easy ones, though that is an inference, not a finding in the advisory. Ge is the only outside researcher named in the critical list, and he found four of the six, while Google’s own researchers found the other two.

Two-thirds of the patch is medium and low severity

The 204 fixes split into 6 critical, 62 high, 82 medium and 54 low, and the arithmetic checks out at 6 plus 62 plus 82 plus 54 equals 204. As shares, that is critical 2.9 percent, high 30.4 percent, medium 40.2 percent and low 26.5 percent, by TechReview’s calculation from SecurityWeek’s severity count. Critical and high together are 68 of 204, exactly one-third, so two-thirds of the patch is medium and low severity.

Use-after-free is the most common flaw type in this release, with 51 occurrences, or exactly 25.0 percent, one in four fixes. Authorisation flaws are nearly tied: incorrect authorisation accounts for 34 and missing authorisation for 16, together 50 of 204, or 24.5 percent, by TechReview’s calculation. The rest of the count is out-of-bounds write and read at 15, uninitialised resource at 14, information leak at 11, UI misrepresentation at 10, improper input validation at 9 and race condition at 8.

Every one of the six critical flaws is a memory-safety bug. Use-after-free, out-of-bounds write and buffer overflow are all failures in how the browser manages memory, and the three types together cover all six critical flaws. Use-after-free alone accounts for 51 of the 204 fixes. The overlap is partial: use-after-free is the most common flaw type overall and appears three times in the critical list, alongside out-of-bounds writes and a buffer overflow. But incorrect and missing authorisation, the overall breakdown’s second- and third-largest categories, do not appear among the six critical flaws, so the critical list is a memory-safety list rather than a miniature of the overall ranking.

The high-severity fixes include a use-after-free in the V8 JavaScript engine, incorrect authorisation in the Omnibox, missing authorisation in Extensions, and memory-lifetime and authorisation issues in Autofill, according to GBHackers. Google handed out 11,000 dollars in rewards for five vulnerabilities reported by external researchers and has yet to determine amounts for 36 flaws, while no reward will be paid for 163 of the 204 flaws, or 79.9 percent, by TechReview’s calculation. One disclosed bounty is 4,000 dollars for CVE-2026-130910, the high-severity ANGLE protection-mechanism failure reported by Arni Hardarson of Neonix Security.

How do I update Chrome to version 158?

Open Chrome’s menu, select Help, then About Google Chrome, and let the browser check for the new build. If version 158.0.8127.36 or .37 is available, relaunch Chrome to apply it. The update is rolling out over days and weeks, so check again if it has not arrived yet.

  1. Click the three-dot menu in Chrome’s top-right corner, then select Help from the menu that appears.
  2. Click About Google Chrome and wait while the browser checks for the latest available build.
  3. Confirm the version shown is 158.0.8127.36 or 158.0.8127.37, the patched builds Google shipped in this release.
  4. Click Relaunch when Chrome prompts you, so the patched build replaces the version now running.
  5. Check again in a few days if the update has not arrived, because the rollout takes weeks.
  6. Update Chrome on every device you use, since the flaws affect the desktop builds on each one.

Access to individual bug details and links may remain restricted until a majority of users are updated, and may continue longer where a flaw affects a third-party library that other projects still need to patch. The release notice itself lists the CVEs, types and components without full technical descriptions. On Linux, update Chrome through your distribution’s package manager instead of the About page, since the browser is installed as a system package there.

914 fixes in six releases

Chrome 158 is the sixth Chrome release, and the fix totals add up. Chrome 156 launched with 353 fixes, then a patch added 52; Chrome 157 launched with 213, a zero-day patch added 9, and a further patch added 83; Chrome 158 now adds 204. That is 914 security fixes across six releases from Chrome 156 to Chrome 158, by TechReview’s calculation from Google’s own figures. Chrome 158’s 204 is 9 fewer than the 157 launch’s 213, about 4 percent smaller, and 149 fewer than the 156 launch’s 353, about 42 percent smaller. The 157 launch’s 213 fixes and the 158 launch’s 204 are close in size, while the 156 launch’s 353 stands out as the largest.

The five full-cycle releases, excluding the 9-fix emergency zero-day patch, carried 28 critical flaws between them, 6 plus 4 plus 7 plus 5 plus 6, by TechReview’s calculation. This release follows the Chrome 157 launch, which shipped 213 security fixes, seven of them critical, and a separate Chrome 157 update less than a week earlier that fixed 83 security flaws, including five critical use-after-free vulnerabilities.

The timeline behind the six critical flaws runs from the first report to the patch in about two months. The first critical report came on 15 September 2026, for CVE-2026-130963 in WebView, and the last came on 26 October, for CVE-2026-130975 in WebAudio, with the patch issued on 17 November. That is a 22-day gap from the last critical report to the patch, and 63 days from the first, by TechReview’s reconstruction from the confirmed report dates.

What to watch next

Whether Google reports active exploitation of any of the 204 flaws, which it has not done so far. Whether Google lifts the access restrictions on the bug reports once most users have the fix. Whether the next stable release continues the pattern of large patches, with more than 200 fixes and a handful of critical flaws. And whether the graphics and media stack keeps producing the most critical flaws, as it has now done in two releases in a row.

The Chrome 158 security update packs 204 fixes, six of them critical, with the worst bugs concentrated in the graphics and media stack and found largely by one outside researcher. Google has not reported any of the flaws being exploited, and the patched builds are already rolling out. That combination is the whole case for updating now rather than later. The patched builds are 158.0.8127.36 and 158.0.8127.37, and the About page will show which one is installed.