Chrome 156 Security Update: 52 Fixes and How to Check Your Version
Google's October 27 Chrome 156 update fixed 52 security issues. See the official versions, four critical CVEs, and how to update safely on Windows, Mac and Linux.
Google released a Chrome 156 security update on October 27, 2026, addressing 52 security issues, including four rated Critical. If you use Chrome on Windows, macOS or Linux, the most useful action is to open More (⋮) → Help → About Google Chrome, let Chrome check for an available update, and select Relaunch if prompted. You do not need an unfamiliar third-party “browser patch” utility.
At a glance: Google lists versions 156.0.8078.73/.74 for Windows and Mac, and 156.0.8078.73 for Linux, in its October 27 desktop Stable announcement. Distribution is gradual. A separate Chrome 157 Early Stable rollout began for a small percentage of Windows users on October 28, so a version number higher than 156 does not necessarily indicate a suspicious installation. Read Google’s October 27 release announcement and its October 28 Early Stable announcement.
Source and testing note (October 29, 2026): This is a research-based guide cross-checked against Google’s release notes and official update instructions. Digital Pulse Brief did not independently exploit the reported flaws, test every operating system, or verify the rollout on a physical computer. Availability and installed versions may change after publication.
Chrome 156 security update: versions at a glance
| Channel and device | Version in official announcement | What it means for you |
|---|---|---|
| Chrome 156 Stable — Windows and Mac | 156.0.8078.73 or .74 | October 27 security maintenance release; availability rolls out gradually |
| Chrome 156 Stable — Linux | 156.0.8078.73 | October 27 security maintenance release for Linux systems |
| Chrome 157 Early Stable — Windows | 157.0.8103.26 or .27 | October 28 early rollout to a small proportion of users; not the same as universal 157 availability |
| Chrome 157 Early Stable — Mac | Not yet announced as rolled out in the October 28 notice | Google said a Mac early-stable rollout would follow; do not assume your Mac should already show 157 |
Important distinction: A release-announcement version is not a promise that every machine already has that build. Google staggers delivery, and organizations may control updates centrally. Use the browser’s own updater to determine what is being offered to your device.
What did Google fix?
Google’s security bulletin says this October 27 release contains 52 security fixes. Four entries are explicitly marked Critical. These are the four issues identified in the published bulletin:
| CVE identifier | Affected component | Issue class reported by Google |
|---|---|---|
| CVE-2026-118306 | FileSystem | Memory corruption |
| CVE-2026-118331 | FileAPI | Improper input validation |
| CVE-2026-118348 | Skia | Improper input validation |
| CVE-2026-118344 | Layout | Use after free |
These terms describe classes of software weaknesses, not proof that someone has already attacked your computer. Google’s announcement does not establish that all four were exploited in the wild; do not confuse a Critical rating with confirmed active exploitation. Full technical details for some bugs may remain restricted while users receive patches. Review the original security bulletin for Google’s exact wording and additional entries.
Why this matters: Browsers process websites, downloads, documents and other complex content. A security bug can exist even if Chrome appears to work normally. Updating the browser addresses known issues without requiring you to recognize a visible error message first.
How to update Chrome on Windows, Mac or Linux
- Save any unfinished work. A browser relaunch can interrupt a form, meeting or upload. Chrome normally restores regular tabs, but do not depend on it to preserve unsaved form data.
- Open the desktop Chrome browser. Use the browser you normally launch, not an installer advertised by a search result.
- Open More (three dots) → Help → About Google Chrome. Chrome checks for available updates on this page. You can also enter
chrome://settings/helpin Chrome’s address bar. - Allow the available update to complete. If the page shows a Relaunch button, select it when you can safely restart the browser.
- Return to About Google Chrome after reopening. Read the version and any update-status message. Do not guess your update status from the desktop shortcut icon.
Google explains that Chrome normally downloads updates in the background and applies them when you close and reopen the browser. Google’s official desktop update instructions also note that regular tabs usually reopen after a relaunch, but Incognito windows do not reopen. Save information you need before restarting.
If your Chrome version is still lower than 156.0.8078.73
First check the update-status message in About Chrome. The most likely next action depends on what you see, not merely on the number:
| What you see | Safer next step |
|---|---|
| Relaunch to finish an update | Save work, relaunch, then recheck the version |
| Chrome says it is up to date, but the published version looks higher | Confirm you are using Stable rather than a managed or alternative channel; the staged rollout or local configuration can explain a difference |
| Browser is managed by your organization | Follow your IT administrator’s update policy rather than overriding management settings |
| Update fails or cannot complete | Check official Chrome update help and your supported OS version; avoid random executables and registry “fixes” |
Do not uninstall Chrome or erase browser data simply because a rollout has not reached your machine. If you are on a work or school computer, your administrator may need to complete a centrally managed update. If you are using an operating system Chrome no longer supports, upgrading that operating system may be necessary; verify compatibility on Google’s current support pages before changing anything.
Why some users see Chrome 157 already
The date is important. Google announced the Chrome 156 Stable security release on October 27, and on October 28 announced an early Chrome 157 Stable release for a small share of Windows users. The latter notice said a Mac rollout would follow. These are separate release-channel announcements, not proof that everyone has moved to 157. Source: Google’s Early Stable update notice.
For ordinary users, the best rule is simple: install the update offered by Chrome’s official update mechanism and confirm the resulting status. Do not switch to Beta or Developer channels, seek a pre-release package or downgrade a working installation merely to make the version number match a headline.
What if you use Chrome on Android, iPhone or a Chromebook?
This particular 52-fix bulletin identifies the desktop Stable channel. Do not reuse its build numbers as if they applied to every mobile browser or Chromebook. Android and iOS Chrome are distributed through their respective app stores, while ChromeOS has its own update history. On October 28, Google separately announced an early Chrome 157 Android rollout to a small percentage of users. It does not mean every Android phone should show 157 that day.
- Android: Check Chrome in Google Play Store under app updates.
- iPhone and iPad: Check for Chrome updates in Apple’s App Store.
- Chromebook: Check ChromeOS system updates and its own release notice rather than applying the Windows/Mac version table above.
See Google’s Chrome update instructions for desktop and mobile and its Android release announcement.
How to confirm you are protected without false reassurance
An updated browser reduces exposure to the known issues fixed in that release; it cannot guarantee safety from every future threat. Use this three-part check:
- Verify the installed browser version and update status in About Google Chrome after the relaunch.
- Compare your platform and channel with Google’s dated official release notes, rather than a screenshot or claim circulating on social media.
- Maintain ordinary safety practices: avoid untrusted downloads, keep your operating system supported and updated, and review unexpected extensions. A security update is not a substitute for sensible account and device security.
If a webpage tells you to install a “critical Chrome security certificate,” paste a command into a terminal or pay to unlock a browser update, do not follow that prompt. Use Chrome’s built-in updater and Google’s own support pages instead.
Frequently asked questions
Does Chrome 156.0.8078.73 fix all Chrome vulnerabilities?
No. Google’s October 27 bulletin describes 52 fixes in that release, not permanent protection against all browser vulnerabilities. Keep receiving future updates.
Is Chrome 157 required immediately?
Google described the October 28 desktop release as Early Stable for a small percentage of Windows users. Use the version that Chrome’s official update service offers your device; do not install an unverified package just to reach 157.
Will updating Chrome delete my tabs?
Google says normal windows and tabs usually reopen after a relaunch, but Incognito windows do not. Save anything important, particularly unsent forms or private-session information, before restarting.
Was one of the four Critical bugs already used in attacks?
The cited Google bulletin does not independently establish that claim. A Critical severity label describes the seriousness of an issue, not necessarily evidence of exploitation in the wild.
Editorial sources and what we verified
This guide combines Google’s October 27 Chrome Stable security bulletin, October 28 Early Stable bulletin, official desktop update steps and Chrome’s update information. The version-comparison and decision tables are original Digital Pulse Brief editorial syntheses of those announcements; they are not screenshots or firsthand penetration-test results. The featured security-fixes chart is an original factual visualization of Google’s reported counts, rendered with QuickChart (public-domain generated output); it is not a Chrome interface screenshot. Technical release information was checked on October 29, 2026. If Google revises a bulletin or your update screen differs, use the current official documentation and consult our corrections policy to flag an inaccuracy.
Browse more verified developments in our App & Software Updates section or consult our Browsers & Web Apps guides for everyday browser troubleshooting.
