Chrome 155 Security Updates Explained: Critical Flaws Fixed, Who's at Risk and How to Update Safely

Chrome is the world's most-used browser, which makes it one of the most attractive targets on the internet. In the past ten days, Google has pushed three security updates that together fix nearly 300 vulnerabilities, including a cluster of critical flaws. If you use Chrome on a laptop, desktop or Android phone, this is a good moment to check your version. This guide explains what was fixed, what the bug types mean, whether you are at risk and exactly how to update.

Counting all three, Google has patched roughly 294 security issues in under two weeks. Google has said updates will continue to reach users over the coming days and weeks, so the version you receive depends on how quickly the rollout reaches your device.

The October 13 release fixed seven critical bugs across graphics, PDF handling, networking, media and core browser components. The critical bugs identified in public reports include:

The ANGLE bug was reported by researcher Zhenpeng "Leo" Lin on September 30. Google's description says that a remote attacker could use a crafted HTML page to execute code outside the sandbox. The PDF flaw CVE-2026-110136 carries a similar description. High-severity bugs in the same release affect V8, Chrome's JavaScript and WebAssembly engine, along with password management, extensions and WebRTC.

The earlier, much larger October 6 release fixed four critical memory-safety issues, all in the use-after-free category. They include CVE-2026-106197 in the browser component, reported by researcher Xinyang Ge on September 11, and flaws affecting navigation and Chromecast. The release also fixed a V8 type confusion bug and numerous high-severity problems across graphics, media and security controls. Google has not published detailed exploitation methods for these issues, and its announcement does not confirm arbitrary code execution.

The third update fixed ten more flaws, among them a use-after-free bug in Prerender, the feature that loads pages in the background to speed up browsing. Some trackers rate the Prerender flaw as critical while others score it high, so the exact severity label varies by source. No exploitation has been reported.

You do not need to be a security expert to understand the main categories:

As of this writing, no. Security trackers covering the October 13 and October 15 releases report that Google has not flagged any of the fixed bugs as exploited in the wild. That makes these updates different from emergency zero-day patches, which Google issues when attacks are already underway.

That does not mean you can relax. After a patch becomes public, attackers can compare the old and new code to work out what was fixed, a process called patch diffing. The period between a fix being released and users installing it is when browsers are most exposed. Critical bugs that can be triggered simply by visiting a malicious page deserve quick action.

If the update does not appear yet, check again later. Google staggers rollouts, so some users receive fixes days after others.

Updating is the most important step, but a few other habits help:

Large batches of fixes can look alarming, but they are normal for a project of Chrome's size. A few reasons explain the numbers:

Still, the volume is a reminder that browsers are among the most exposed software on any device.

"If Google hasn't reported an attack, I can skip the update."

Not wise. Exploits can appear quickly after patches are published.

"I use incognito mode, so I'm safe."

Incognito affects local history, not the browser's security. A memory flaw can be triggered in any window.

"Only Windows is affected."

The updates apply to Windows, Mac, Linux and Android, with some flaws specific to certain platforms.

What is the latest Chrome version?

At the time of writing, Chrome 155.0.8059.84/.85, released on October 15, 2026.

How many vulnerabilities were fixed?

Roughly 294 across three updates: 247 on October 6, 37 on October 13 and 10 on October 15.

Are the flaws actively exploited?

No exploitation in the wild has been reported for these updates.

Do I need to restart Chrome?

Yes. Updates only take effect after you relaunch the browser.

How do I check my Chrome version?

Type chrome://version in the address bar or open Help, then About Google Chrome.

Should I update Edge and other browsers?

Yes. They share Chromium code and receive separate updates, so check each one.

Three updates in ten days and nearly 300 fixes make this one of the busiest stretches of the Chrome 155 cycle. The good news is that no exploitation has been reported and the fix takes only a minute. Open About Google Chrome, relaunch the browser and confirm your version. That small habit is one of the most effective security steps you can take.