Skip to content
audiotale.net
Sign in
NewsNews

Chrome 158 stable: 204 security fixes, 6 Critical, update to 158.0.8127.36

Google's 17 November release fixes 204 security bugs, six rated Critical; here is what changed, which versions to look for and how to update.

audiotale.net team

· 6 min read

Written by AI from the sources linked below. How we use AI

On this page
  1. Key points
  2. What to do
  3. What happened
  4. Background
  5. The numbers
  6. What it means
  7. What we don't know yet
  8. What to watch next
  9. Sources

Google promoted Chrome 158 to the stable channel on 17 November 2026 with 204 security fixes, six of them rated Critical. If you run Chrome on Windows, Mac or Linux, the version to look for is 158.0.8127.36 (Linux) or 158.0.8127.36/.37 (Windows and Mac). Android has its own build, 158.0.8127.42, and the Extended Stable channel got a separate update with 79 security fixes.

The notice does not say that any of these bugs is being exploited in the wild, and we found no independent coverage of the release yet, so everything below comes from Google's own Chrome Releases posts.

Key points

  • Chrome 158 (158.0.8127.36 on Linux, 158.0.8127.36/.37 on Windows and Mac) went to the stable channel on 17 November 2026 and includes 204 security fixes.
  • By Google's severity labels the 204 fixes split into 6 Critical, 62 High, 82 Medium and 54 Low.
  • The six Critical bugs are CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054 and CVE-2026-130975.
  • Twelve entries credit Anthropic, and eight of them say the researcher was "assisted by Claude".
  • Chrome for Android 158.0.8127.42 carries the same security fixes as desktop; Extended Stable moved to 156.0.8078.108/.109 with 79 fixes.

What to do

  • Update now. Open the menu, choose Help, then About Google Chrome. Chrome downloads the update and asks you to relaunch. A tab left open for days still runs old code until you restart.
  • Check your version. On desktop you want 158.0.8127.36 or later. On Android you want 158.0.8127.42 once it reaches Google Play, which Google says will take a few days.
  • Managed fleets on Extended Stable should target 156.0.8078.108/.109 on Windows and Mac, which Google says carries 79 security fixes.
  • Other Chromium browsers (Edge, Brave, Opera, Vivaldi and others) ship their own updates that pick up Chromium fixes. Check each vendor's release notes, as we have not confirmed their timing.
  • Electron and embedded WebView apps may lag the browser, so keep an eye on your own app vendors.
  • Google says rollout "will roll out over the coming days/weeks", so not everyone sees the update at once. Restricting bug details until most users are updated is normal practice for the Chrome team.

What happened

On Tuesday 17 November 2026, the Chrome Releases blog announced the promotion of Chrome 158 to the stable channel for Windows, Mac and Linux. The post lists every security fix with an internal bug number, a severity, a CVE identifier, a component, the reporter and the date it was reported. Google notes that access to bug details may stay restricted until most users have the fix, and longer if the bug sits in a third party library that other projects have not yet patched.

The counts below come from our own tally of the entries in that post.

Chrome 158 security fixes by severityfixes
Chrome 158 security fixes by severity (fixes)
fixes
Medium82
High62
Low54
Critical6

Source: Chrome Releases, Stable Channel Update for Desktop, 17 November 2026

The six Critical entries are:

  • CVE-2026-130963: use after free in WebView, reported by Google on 15 September.
  • CVE-2026-131031: out of bounds write in GPU, reported by Xinyang Ge (Anthropic), assisted by Claude, on 7 October.
  • CVE-2026-131060: buffer overflow in Media, reported by Xinyang Ge (Anthropic), assisted by Claude, on 13 October.
  • CVE-2026-131008: use after free in GarbageCollection, reported by Xinyang Ge on 17 October.
  • CVE-2026-131054: out of bounds write in ANGLE, reported by Google on 22 October.
  • CVE-2026-130975: use after free in WebAudio, reported by Xinyang Ge (Anthropic) on 26 October.

Most entries list no bounty (the post shows N/A or TBD). Only five carry a reward in the post: $4,000, $2,000, $2,000, $1,000 and $2,000, which adds up to $11,000 across the listed payments. Several others are marked "TBD", meaning the reward had not been decided when the post went up.

Background

Chrome ships a new major version on a regular schedule, and each stable release carries a batch of fixes found by Google's own teams, outside researchers and automated tooling. Google credits its fuzzers and sanitizers in every notice, naming AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer and AFL.

What stands out in this release is the number of entries and who found them. By our count, 145 of the 204 entries are credited to Google itself. Twelve name Anthropic: seven list Xinyang Ge as "Anthropic, assisted by Claude", one lists Vlad Stolyarov (Anthropic) as assisted by Claude, one lists Xinyang Ge (Anthropic) without the Claude note, and three, all in the Media and PerformanceAPIs components, credit "Anthropic and Ada Logics". Another seven entries name Xinyang Ge without an affiliation.

Anthropic recently shortened its own disclosure window for high and critical flaws it finds; we covered that in Anthropic cuts bug disclosure window to 30 days. The Chrome notice shows what that work looks like from the receiving end: reports dated from late September to late October, fixed in a release a few weeks later. For a related view of the attacker side, see Google's GTIG exploit agent.

The numbers

The 204 fixes are not evenly spread. By our tally of the component named in each entry, the most frequent are DevTools (12), ANGLE (10), Autofill (10), Media (9), GPU (8), WebAppInstalls (8), Extensions (7) and V8 (7).

By bug type, use after free is the biggest single class with 51 entries, followed by incorrect authorization (34), missing authorization (16), uninitialized resource (14), information leak (11) and UI misrepresentation (10).

Chrome 158 fixes by the most common bug typesfixes
Chrome 158 fixes by the most common bug types (fixes)
fixes
Use after free51
Incorrect authorization34
Missing authorization16
Uninitialized resource14
Information leak11
UI misrepresentation10

Source: Chrome Releases, Stable Channel Update for Desktop, 17 November 2026 (our tally)

Use after free bugs are memory errors where code keeps using an object after it has been freed. They are the classic route to running attacker code in a browser. The long tail of authorization bugs is a different kind of problem: a feature that should check a permission or origin and does not.

What it means

For everyday users: restart the browser. A fix that is downloaded but not applied protects no one.

For IT teams: 204 fixes in one release is a lot of surface to verify, and Critical bugs in the GPU, ANGLE, Media and WebAudio components are in components that process web content. Treat this as a priority patch cycle even though no exploitation is reported. Extended Stable moved to 156.0.8078.108/.109, which keeps managed browsers one step behind the newest major version.

For developers: if your product embeds Chromium or Android WebView, one Critical entry is a use after free in WebView (CVE-2026-130963). Check how your framework picks up engine updates.

For security researchers: the credit lines show AI-assisted bug finding turning up in the output of one of the most heavily fuzzed code bases in the world. Whether that counts as a trend depends on what future releases show.

What we don't know yet

  • Whether any of the 204 bugs has been exploited. The post does not say, and that is not the same as confirming none was.
  • The details of the bugs. Google restricts bug links until most users have updated.
  • When Edge, Brave and other Chromium browsers will ship matching fixes.
  • The final bounty amounts for entries marked "TBD".
  • Independent analysis. We found no outside coverage of the release when we checked, so the severity labels and counts rest on Google's own post.

What to watch next

  • The Chrome Security page and bug tracker, as restrictions on bug details lift.
  • Android's Google Play rollout of 158.0.8127.42.
  • Any out-of-band 158 point release if a bug turns out to be exploited.
  • Vendor updates for other Chromium-based browsers.

Sources

Written by

audiotale.net team

The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.