SOCLYDE logo
Current languageEN
Cybersecurity newsChromeVulnerabilitiesSecurity updates

Chrome 155 fixes four critical vulnerabilities

Google ships 247 security fixes in Chrome 155, including four critical flaws. Check the installed version and restart browsers across your team.

Published on

By Soclyde Team

A shop owner uses a desktop computer at a bicycle repair workshop counter

In summary

  • Chrome 155 includes 247 security fixes, with four rated critical.
  • The October 6 advisory does not report exploitation of these flaws.
  • Check the version actually running after restarting Chrome.

Explore next

Soclyde resources

Article contents

Google released a Chrome 155 security update for Windows, macOS and Linux on October 6, 2026. It contains 247 security fixes, including four critical vulnerabilities. For a small business using the browser for banking, invoicing and email, the immediate task is to confirm that the corrected version is actually running on every workstation.

What Chrome 155 fixes

The four critical defects involve use of freed memory in Chromecast, Browser, Navigation and Track. Their identifiers are CVE-2026-106382, CVE-2026-106197, CVE-2026-106358 and CVE-2026-106347. Security NEXT and SecurityWeek corroborate the scope of Google's release.

This is a browser security update. It is not a breach notification from a business that happens to use Chrome.

A fix does not establish an attack

The advisory does not report exploitation of these vulnerabilities in the wild. A critical rating supports prompt patching, but it does not show that anyone accessed your accounts.

Do not turn the number of fixes into a count of victims. An incident response decision needs evidence about the specific workstation or account, alongside the vendor bulletin.

Check the version after relaunching

Google lists stable versions 155.0.8059.39/.40 for Windows and macOS, and 155.0.8059.39 for Linux. Open About Google Chrome, allow the offered update to complete, and relaunch the browser.

Save unfinished forms and work beforehand. Once Chrome restarts, read the displayed version again. On managed workstations, ask the IT owner to check the deployed package and release channel.

Protect the accounts used in Chrome too

An updated browser and distinct passwords address complementary needs. Patching closes software flaws; a unique secret limits reuse of a password exposed on another account.

Review professional credentials kept in the browser using our password manager or browser comparison. That review does not replace protection of sessions that are already signed in.

Make the check manageable for a small team

Assign someone to check shared computers, laptops that rarely connect and work profiles. Record devices still awaiting a restart or assistance. Saying that updates are automatic does not confirm the state of the fleet.

Schedule restarts around sales and accounting work. Keep track of exceptions so an absent laptop receives attention when it returns, rather than disappearing from the checklist.

The connection with Soclyde

Soclyde keeps the encrypted vault on your devices and lets you organise distinct credentials. That separation helps manage professional accounts used in Chrome without scattering their passwords across browser profiles.

The vault does not patch Chrome or independently protect an active session on a compromised computer. Explore Soclyde features for the credential management part of this work.

What to remember

Install the corrected version, restart Chrome and check the running version on computers that access sensitive services. This bulletin does not establish account theft. To pair browser maintenance with better credential organisation, read our password security guide.

Frequently asked questions

Which Chrome versions include these fixes?

The October 6 advisory lists Chrome 155.0.8059.39 or .40 for Windows and macOS, and 155.0.8059.39 for Linux. A later stable version may also include the fixes. Check the version after relaunching Chrome.

Should everyone change their passwords?

A security release does not prove credential theft. Without evidence of compromise, start by updating the browser. If your team identifies an intrusion, follow its procedure for replacing exposed secrets and sessions from a trusted device.

Does a password vault replace the update?

No. Browsers process pages and use authenticated sessions. They need security updates regardless of where passwords are stored. Soclyde helps organise distinct credentials; it does not repair Chrome vulnerabilities.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading