Chrome 155 Release Date, Version Number and What's New

Chrome 155 is now on the stable channel for Windows, Mac and Linux as of October 6, 2026, landing as version 155.0.8059.39/.40 on Windows and Mac and 155.0.8059.39 on Linux. Unlike some recent releases, this one is not a feature update: Google's own Chrome Releases post describes it purely as a security update, patching 247 vulnerabilities, four of them rated Critical, with no new user-facing features called out.

Chrome 155 release date and rollout

Google published its "Stable Channel Update for Desktop" post on chromereleases.googleblog.com on Tuesday, October 6, 2026, confirming that the stable channel "has been updated to 155.0.8059.39/.40 for Windows and Mac and 155.0.8059.39 to Linux which will roll out over the coming days/weeks." That phrasing is standard Chrome language for a staged rollout, so not everyone sees the update the moment it is announced — Chrome checks for updates periodically and applies them in the background, and a small percentage of the install base is held back in case a regression turns up.

The same week also brought Chrome for Android and a Chrome Beta push for both desktop and iOS, according to the blog's own October 2026 archive, which lists "Chrome for Android Update" on October 6 and "Chrome Beta for Desktop Update" and "Chrome Beta for iOS Update" on October 7. That lines up with the pattern this release cycle followed: mobile and early-stable channels moved first, with the broad desktop stable push landing a few days later.

Chrome 155 version number, confirmed

If you only need one number, here it is straight from Google: desktop stable is 155.0.8059.39 (or .40, depending on platform and build) for Windows and Mac, and 155.0.8059.39 for Linux. Google's linked changelog, which covers every commit between the previous release and this one, is scoped to the range 154.0.8037.99..155.0.8059.40 — which also confirms the final build number for Chrome 154 for anyone tracking the jump between versions.

To check your own copy, open chrome://settings/help (or Chrome menu → Help → About Google Chrome). If a newer build is available, the browser will start downloading it automatically and prompt you to relaunch.

What Chrome 155 actually fixes: 247 security bugs

The headline number in Google's post is 247 security fixes in this build. That is a large patch batch by Chrome's recent standards — for comparison, last month's Chrome 154 security update fixed 108 bugs, 11 of them Critical. Chrome 155 flips that ratio: far more total fixes, but fewer Critical-severity ones.

Google's post notes the usual caveat on disclosure: "Access to bug details and links may be kept restricted until a majority of users are updated with a fix," and the same restriction applies to any bug that lives in a third-party library other projects still depend on. Full technical writeups for fixed bugs eventually surface through the Chrome Security Page once that restriction lifts. That is why a chunk of the entries in the published list show "N/A" or "TBD" instead of a bounty amount — the reward hasn't been finalized, or the bug was found internally and isn't eligible for a cash reward in the first place.

How Chrome defines Critical, High, Medium and Low

Chrome's own severity guidelines define the four tiers used in every one of these release posts. Critical covers bugs that let an attacker run arbitrary code outside Chrome's sandbox with little or no user interaction — the worst case for a browser bug. High generally means code execution is possible but requires the sandbox to also be bypassed, or that the bug otherwise causes serious data loss. Medium and Low cover things like information leaks, denial-of-service conditions, or bugs that need unusual configurations or significant user interaction to exploit. That scale is why four Critical bugs in Chrome 155 is the number worth paying attention to, even though it's a small fraction of the 247 total fixes.

The four Critical bugs fixed in Chrome 155

All four Critical-severity issues in this release are use-after-free bugs, which is the single most common root cause behind Chrome's Critical bugs in general — a piece of memory gets freed while something else still holds a pointer to it, and an attacker who can control what gets allocated into that freed slot can hijack execution. Per Google's published list:

• CVE-2026-106382 — use after free in Chromecast, reported by Google internally.
• CVE-2026-106197 — use after free in Browser, reported by external researcher Xinyang Ge.
• CVE-2026-106358 — use after free in Navigation, also reported by Xinyang Ge, credited as "assisted by Claude."
• CVE-2026-106347 — use after free in Track, again from Xinyang Ge, also credited as "assisted by Claude."

Three of the four Critical fixes trace back to the same outside researcher, and two of those four credits explicitly note AI assistance in finding the bug — a small but notable data point in a disclosure list that is otherwise dominated by Google's own internal fuzzing and sanitizer tooling (the post separately thanks researchers who use AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer and AFL during Chrome's development cycle, catching bugs before they ever reach a stable build).

Bug bounty rewards in this release

Chrome's Vulnerability Rewards Program pays out for externally reported bugs once Google confirms and fixes them, and this release's list shows rewards ranging from $1,000 up to $5,000 among the entries that have a finalized amount so far (many others are still marked TBD, meaning the reward hasn't been set yet). The largest confirmed payout in the Chrome 155 list is $5,000, for a High-severity "Incorrect Authorization in SiteIsolation" bug (CVE-2026-102322) reported by researcher Avadhut Mahamuni. Several other High-severity fixes — mostly uninitialized-resource bugs in ANGLE, Chrome's graphics abstraction layer — carried $2,000 rewards.

Which parts of Chrome got patched the most

Breaking down all 247 entries in Google's list by the Chromium component they touch shows where this release's engineering effort actually went. The "Mobile" component (Chrome for Android-specific code paths, patched alongside desktop because the underlying Chromium codebase is shared) tops the list, followed by Media and ANGLE, Chrome's cross-platform graphics abstraction layer that sits in front of each OS's native graphics API.

ANGLE and V8 bugs are worth flagging specifically: both sit close to the browser's attack surface for untrusted web content (ANGLE processes GPU commands triggered by WebGL pages, V8 runs every script on every page you visit), so fixes there tend to carry more real-world exploitation risk than, say, a UI misrepresentation bug in a settings dialog.

Does Chrome 155 add any new features?

Short answer, per Google's own announcement: no. The official "Stable Channel Update for Desktop" post for Chrome 155 is exclusively a security bulletin — version numbers, the fix count, the CVE list, and the standard boilerplate about release channels and bug reporting. There is no features section, no mention of a JPEG XL decoder, no post-quantum/ML-KEM cryptography callout, and no note about Android permission-prompt changes in this particular post. If any of those land, they would typically show up either in a separate "New in Chrome" developer post, in the Chrome Platform Status feature tracker, or in a beta-channel announcement — none of which currently lists them tied to M155 at the time of writing. Readers searching for "Chrome 155 new features" should treat this release as what Google itself calls it: a stability-and-security maintenance build, not a feature release.

How Chrome 155 compares to Chrome 154

Two back-to-back releases billed purely as security updates is unusual but not unheard of — Chrome's four-week major-version cadence means a release can land in the same window as a backlog of bug fixes clearing Google's internal review, independent of whether any new web platform feature happens to be ready to ship at the same time.

How to update to Chrome 155

Chrome updates itself automatically in the background on Windows, Mac and Linux, but you can force the check manually:

1. Click the three-dot menu in the top-right corner of Chrome.
2. Go to Help → About Google Chrome (or type chrome://settings/help into the address bar).
3. Chrome will check for an update and, if 155.0.8059.39/.40 (or later) isn't already installed, download it automatically.
4. Click Relaunch to apply the update. Your tabs will reopen automatically.

Because four of the fixes in this release are Critical-severity memory-safety bugs, there's no real reason to delay the relaunch once the update has downloaded — Critical bugs are, by Chrome's own severity definitions, the ones that can lead to remote code execution outside the sandbox with little or no user interaction.

A few platform notes worth knowing:

• Windows and Mac: Chrome updates silently in the background via its own updater service; the manual check above just speeds that up.
• Linux: if you installed Chrome from Google's own .deb/.rpm repository, your system package manager will pick up 155.0.8059.39 the next time it refreshes; distro-maintained Chromium builds follow their own packaging schedule and may lag behind.
• Managed/enterprise devices: IT administrators can hold or stagger this rollout through Chrome Browser Cloud Management or group policy, which is part of why Google phrases its own rollout timeline as "days/weeks" rather than promising same-day delivery to every machine.

Chrome 155 on Android and iOS

This desktop rollout follows the pattern described by Google's own release calendar and blog archive: mobile builds and early-stable channels typically move first, with the full desktop stable push following within the same week. The Chrome Releases blog's October archive lists a "Chrome for Android Update" published the same day as the desktop stable post, alongside Chrome Beta pushes for desktop and iOS the following day — consistent with Chrome's usual staggered cadence across platforms rather than a single simultaneous release.

What's next

With 155 now on stable, attention shifts to the next four-week cycle and whatever accumulates on the beta channel in the meantime — Google's Chrome Platform Status tracker and the "New in Chrome" developer blog are the places a feature-carrying release would actually get documented, separately from the Chrome Releases security bulletins. If you're layering extra protection on top of browser patches — for example because you're on public Wi-Fi a lot — our guide to how a VPN works and whether you need one is a reasonable next read. For now, the practical takeaway for Chrome 155 is simple: it's a large, Critical-severity-inclusive patch batch, not a new-feature release, and the fix is already rolling out — update and relaunch when Chrome prompts you to. If you want to track future releases yourself, Google explains how to move between stable, beta, dev and canary builds on its release channels page, and security researchers can report new findings directly through the Chromium issue tracker.

Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Felix MoreauAll Software & Guides coverage