Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsGoogle’s Chrome 155 Stable release, announced October 6, 2026, reports 247 security fixes. Google is rolling it out in stages over the coming days and weeks. Update Chrome when the release reaches your device, then restart the browser if prompted.
What Chrome 155 fixes
Google’s release listing reports 247 security fixes. That is the company’s wording; the headline’s “vulnerabilities” is shorthand, not a claim that every issue has a fully public technical description. Google says details may remain restricted until most users have received the fix, or while third-party library fixes are pending elsewhere. Chrome Releases
The listing identifies four critical use-after-free issues:
- CVE-2026-106382: Chromecast; reported by Google on July 15, 2026.
- CVE-2026-106197: Browser; reported by Xinyang Ge on September 11, 2026.
- CVE-2026-106358: Navigation; reported by Xinyang Ge (Anthropic), assisted by Claude, on September 28, 2026.
- CVE-2026-106347: Track; reported by Xinyang Ge (Anthropic), assisted by Claude, on September 30, 2026.
Google also lists high-severity issues in components including SiteIsolation, ANGLE, Autofill, Translate, Fonts, Proxy, Omnibox, WebGL, Dawn, Video, V8, WebRTC, Media, and PDF. The published severity labels and component names do not establish that all issues are exploitable remotely in the same way, and the release note is not a complete public technical analysis.
Recommended Free Tools
#1 Best Overall
Chrome 155 versions by platform
| Platform | Chrome 155 version listed | Availability |
|---|---|---|
| Windows | 155.0.8059.39/.40 | Staged rollout over the coming days and weeks |
| Mac | 155.0.8059.39/.40 | Staged rollout over the coming days and weeks |
| Linux | 155.0.8059.39 | Staged rollout over the coming days and weeks |
| Android | 155.0.8059.39 | Google Play rollout over the following days |
| iOS | Not stated for Chrome 155 in the release listing | Chrome on iOS relies on Apple’s WebKit security process; update iOS for WebKit fixes |
Build numbers and rollout timing are from Google’s Chrome release listing. Google says Android releases include the same security fixes as the corresponding desktop release unless otherwise noted. On iOS, Chrome uses Apple’s WebKit security process, so Chrome desktop release details should not be treated as the iOS update schedule. Chromium’s Chrome Security Update FAQ
How to update Chrome
- Open Chrome and select the three-dot menu in the upper-right corner.
- Choose Help, then About Google Chrome. Chrome checks for available updates on this page.
- If Chrome downloads an update, select Relaunch to apply it. Save any work in open tabs first; the browser restarts.
- If version 155 is not offered yet, check again later. Google is distributing this release gradually, so its absence during the rollout does not by itself mean the browser is stuck.
For Android, check Chrome’s listing in Google Play and install the update when it appears. Google says the Android rollout will take place over the following days. On iPhone or iPad, install relevant iOS updates through Apple’s update settings.
Rank #2
Do you need to update Chrome now?
Yes. Install the update when it becomes available and restart Chrome so the fixes take effect. The Chrome Security team advises applying updates as soon as they are available rather than trying to rank them by the public details. Its FAQ states: “The most secure option is to automatically update Chrome as soon as any update is available, independent of the specific details of any security fixes included in the update.” Chrome Security Update FAQ
Google’s release cadence includes Stable milestones every two weeks and planned weekly security refreshes. Its September 8, 2026 developer post says Extended Stable remains an option for customers that cannot accommodate the two-week feature cycle; security fixes continue to be backported regularly each week, while major feature updates arrive every eight weeks. These cadence details describe Google’s release approach, not a reason for individual users to delay security updates. Chrome for Developers
Free tools Windows power users keep installed
One-click scans. No signup required.
What the 247-fix count does—and does not—tell you
The number is Google’s reported total for Chrome 155’s security fixes. It does not mean every fix has a public CVE description or that all 247 issues have the same severity, exposure, or exploitability. Google’s restricted-disclosure policy means some details can be withheld while users receive the update or while shared dependencies are being patched. The listed critical and high-severity items are examples in the release notice, not a full accounting of the technical risk of every fix.
For context only, the Chrome Security Team said it fixed 1,072 security bugs across Chrome 149 and 150 combined. That earlier aggregate covers two different milestones and should not be added to or confused with Chrome 155’s reported count. Chrome Security Team
