•
•
•
•
•
•
•
Google’s October 15, 2026 stable release for Chrome 155 includes 10 security fixes, including a critical prerender use-after-free flaw. Check affected platforms and update safely.
Google’s Chrome team announced a stable desktop update on October 15, 2026: version 155.0.8059.84/.85 for Windows and Mac, and 155.0.8059.84 for Linux. The release includes 10 security fixes, including a critical use-after-free vulnerability in prerendering and several high-severity memory-safety issues.
The update is rolling out gradually, so availability can vary by device and managed environment. Check Google’s official Chrome Releases blog for the latest version and platform-specific notes.
| Detail | Information |
|---|---|
| Stable desktop release date | October 15, 2026 |
| Windows and Mac versions | 155.0.8059.84/.85 |
| Linux version | 155.0.8059.84 |
| Security fixes listed | 10 |
| Critical issue | CVE-2026-110922, use-after-free in prerender |
| Recommended action | Update Chrome and relaunch the browser |
Google’s release notes list the following examples:
A use-after-free flaw can occur when software accesses memory after it has been released. Memory-corruption bugs can have serious consequences, but actual impact depends on the flaw, browser protections and the circumstances of exploitation. Do not assume every listed issue is being actively exploited: Google’s release notes do not state that for every vulnerability.
Anyone using Chrome on Windows, macOS or Linux should check for the latest stable release. Chrome for Android also received version 155.0.8059.84 on October 15, according to Google’s release blog.
Organisations using centrally managed browsers should follow their IT team’s rollout policy and confirm which versions are approved. Other Chromium-based browsers may receive fixes on a different schedule; check the relevant vendor’s advisory rather than assuming Chrome’s version number applies.
On a desktop computer:
On Android, open the Google Play Store, search for Google Chrome and select Update if available. Rollouts can take time, so check again later if the update has not yet appeared.
Only download Chrome updates through Chrome’s built-in updater or the official Google distribution channel. Avoid third-party download sites and unsolicited update pop-ups.
IT teams should confirm browser inventory, prioritise devices on older vulnerable builds, test compatibility for critical workflows and verify that updates have completed. If updates are managed centrally, review policy and compliance reporting rather than relying on users to update manually.
Security teams should also review the official advisory for any changes to vulnerability details. A release note is a starting point; it does not replace monitoring, endpoint protection or broader security practices.
The October 15 stable release includes fixes for a critical prerender use-after-free flaw and several high-severity issues. Users should install the latest stable update.
Google listed 155.0.8059.84/.85 for Windows and Mac in the October 15 desktop release. Later updates may supersede these versions.
No. The release notes list vulnerabilities and fixes; they do not say that every issue was exploited in the wild.
Google rolls updates out over time. Managed devices may also receive updates according to an organisation’s deployment policy.
Google’s Chrome Releases blog and Chrome security release notes are the primary sources.
Chrome’s October 15, 2026 stable release includes 10 security fixes, among them a critical prerender vulnerability and several high-severity memory-safety issues. Update through Chrome’s built-in updater, relaunch the browser and verify the installed version. Organisations should use official release notes and device inventory to ensure the update reaches all applicable systems.
This article was authored and reviewed by Wipidia's technical editorial desk in Jalandhar, Punjab. Every code snippet, algorithm breakdown, and strategic framework is independently tested against live production standards before publication.
