IT & SecurityCreated on October 28, 20262 min read

Chrome 156: 52 security fixes, then one important step: relaunch

The October 27 desktop update includes critical fixes. Check the running browser after the update, including on developer workstations.

What changed

Google’s October 27 stable update contains 52 security fixes, including critical FileSystem and FileAPI issues. The announced builds are 156.0.8078.73/.74 for Windows and macOS, and 156.0.8078.73 for Linux. Rollout is gradual.

Why it matters

This is a browser update. A change to your website cannot patch Chrome on a visitor’s computer. Developers should also inventory separate Chromium copies bundled with browser testing tools; updating the desktop application does not prove those copies are patched.

What to do

Use Chrome’s official update mechanism, or your organisation’s managed software channel, then relaunch the browser.
Check the running build after relaunch. If a managed device cannot receive the release yet, report that limitation to its administrator.

Reference commands

Open these addresses in Chrome to check the installed build

chrome://settings/help
chrome://version

Verify the result

Record the browser version and platform, not just the installer download. Re-test your application’s key browser flows after the update. This release notice does not by itself establish active exploitation.

Official sources

Take it into your project

Get the files, keep the guide, or give your coding assistant a ready-to-use brief.

Download guideMarkdown Download AI setup briefEnglish · Markdown

Set it up with AI

Copy this English prompt into your coding assistant. It includes the article, available files and project setup steps.

View the setup prompt

AI setup prompt · English

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/chrome-156-october-27-security-update?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Review the official Chrome release dated 27 October 2026: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html . Inventory Chrome used for development and administration, plus separately bundled Chromium in browser automation. The desktop release is 156.0.8078.73/.74 for Windows and macOS, and 156.0.8078.73 for Linux. Follow the official supported stable-channel update path and relaunch guidance. Do not assume a website code change patches visitors’ browsers, or that updating Chrome updates Playwright/Puppeteer bundled browsers. Report exact running versions, rollout limitations and unverified systems. Do not disable security settings or run exploit tests.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.

The prompt

Review the official Chrome release dated 27 October 2026: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html . Inventory Chrome used for development and administration, plus separately bundled Chromium in browser automation. The desktop release is 156.0.8078.73/.74 for Windows and macOS, and 156.0.8078.73 for Linux. Follow the official supported stable-channel update path and relaunch guidance. Do not assume a website code change patches visitors’ browsers, or that updating Chrome updates Playwright/Puppeteer bundled browsers. Report exact running versions, rollout limitations and unverified systems. Do not disable security settings or run exploit tests.

Read the original sourceGoogle · Chrome stable release · 27 October

Chrome 156Browser securityUpdates