The reported 247-fix and 37-fix totals refer to two separate Chrome 155 desktop updates, not competing counts for the same release. SecurityWeek linked 247 fixes, including four critical vulnerabilities, to the earlier build family; Malwarebytes and Neowin linked 37 fixes, including seven critical vulnerabilities, to the later one.
Google Chrome Releases dated its desktop update pages October 6 and October 13, 2026. Those dates identify the pages, while the reported totals and builds come from the outlets covering each release: SecurityWeek’s account of the earlier update, and Malwarebytes and Neowin’s account of the later update. The corresponding Google Chrome Releases page is dated October 6; the later page is dated October 13.
Two Chrome 155 updates, two build groups
The build numbers make it easier to match each report to the update it describes. Windows and macOS had separate reported build numbers within each release; Linux had its own.
| Google Chrome Releases page date | Windows and macOS builds | Linux build | Reported vulnerabilities fixed | Reported critical vulnerabilities |
| October 6, 2026 | 155.0.8059.39 and 155.0.8059.40 | 155.0.8059.39 | 247 | 4 |
| October 13, 2026 | 155.0.8059.79 and 155.0.8059.80 | 155.0.8059.79 | 37 | 7 |
Chrome for Android
Malwarebytes reported Android version 155.0.8059.79 for the October update and said availability through Google Play could lag for some users. Google Chrome Releases dated its Chrome for Android update page October 13, 2026.
Check Chrome for an update manually
In Chrome, open About Google Chrome from Settings or Help. Chrome checks for an update there; if it offers one, select Relaunch to apply it. Malwarebytes described this update path and reported that Chrome updates could roll out over days and weeks.
