Chrome's biggest patch in months: 213 fixes, seven critical

Chrome 157 fixes 213 security flaws, seven rated critical; update now, no attacks reported

From the HARD Situation Room · First reported

Google released Chrome 157 on 3 November for Windows, Mac and Linux, with an Android build on Google Play. It fixes 213 security flaws, seven of them rated critical, mostly memory bugs in graphics and page-loading code. Coverage says Google has not reported any being exploited, and the rollout is staged over days or weeks.

What to do this week

  1. Update Chrome now.Open Chrome, click the three dots at the top right, then Help, then About Google Chrome. Chrome checks for updates and downloads one if it's waiting. You should see a version beginning 157, ideally 157.0.8103.38 or higher.
  2. Click Relaunch.The fix doesn't apply until Chrome restarts. Your open tabs normally come back. If you never close the browser, this is the step that's been missed.
  3. On Android, update through Google Play.Open Google Play, search for Chrome and tap Update if you see it. It may not appear for a few days.
  4. Check the computers of parents and relatives.A five-minute call or visit now is easier than cleaning up after a hijacked browser. If someone manages devices for your household or family office, ask them to confirm Chrome is on version 157.
  5. Ignore pop-ups telling you to update.Fake "your browser is out of date" messages are a common way to deliver malware, and news of a big patch brings more of them. Only update from Chrome's own menu.

Or have someone do it. Keeping every family device patched, and noticing the one that quietly isn't, is exactly what private cybersecurity is for.

What happened

On 3 November, Google released Chrome 157 to everyone on Windows, Mac and Linux. It fixes 213 security flaws, and Google rates seven of them critical, its highest level. An Android version, 157.0.8103.38, is arriving through Google Play over the following days.

Chrome 157CVE-2026-121156, CVE-2026-121229, CVE-2026-121035 and others
Severity
Critical 7 critical, 77 high, out of 213 fixes
Fixed in
157.0.8103.38 (Windows and Mac get .38 or .39, Linux .38, Android .38)
Affects
Chrome on Windows, Mac, Linux and Android, in versions before 157
Attacks seen
None reported by Google
Rollout
Staged over days to weeks
What's known.Version numbers and the fix count are consistent across Malwarebytes[1] and other coverage. Breakdown by severity is from SmartScope[2].

Most of the critical flaws are memory bugs, the kind where a program mishandles the space it uses to hold data. They sit in the parts of Chrome that draw web pages and handle graphics. Malwarebytes[1] describes three. A flaw in ANGLE, Chrome's graphics layer, could let a crafted web page run code outside Chrome's protective sandbox. A flaw in Prerender, which loads pages in the background before you click, could cause a crash or, in some cases, let an attacker run their own code. A third, in Dawn, which powers Chrome's WebGPU graphics feature, could do the same.

Google has not said any of the 213 flaws are being used in attacks, according to Daily Security Review[3]. It is also holding back some technical detail until more people have updated. That is normal practice, but attackers often study a patch once it is public, so the window between release and your update matters.

The full story1 more section

Who is affected

Anyone running Chrome before version 157, on a computer or an Android phone. That includes the family laptop, a parent's desktop that is rarely restarted, and a work machine you use for banking or email.

Chrome normally updates itself quietly. It falls behind when the browser is never fully closed, which describes plenty of people with fifty tabs open for weeks, or when something on the computer is blocking the update. The rollout is also staged, so your copy may simply not have been offered the update yet.

Two smaller notes. Windows and Mac machines on Chrome's Extended Stable channel, mainly used by organisations, moved to version 156.0.8078.88 with 55 security fixes, three of them critical, according to SmartScope[2]. And browsers built on Chrome's engine, such as Edge and Brave, run on the same underlying code, so look for their own updates too.

A browser is the one program that opens every stranger's page you click on. Keeping it current is the cheapest protection you have.

Timeline
  1. HARD publishes its article, at High.

References4
  1. ^ Malwarebytes (). “Chrome 157 fixes 213 security issues, including 7 critical flaws”. Release date, versions, 213 fixes with seven critical, three critical flaws described, how to update.
  2. ^ SmartScope (). “Chrome 157: Stable Released with 213 Security Fixes and 7 Critical Flaws”. Severity breakdown (7 critical, 77 high), list of seven critical CVEs, Extended Stable 156.0.8078.88, Android details.
  3. ^ Daily Security Review (). “Chrome 157 Fixes 213 Security Flaws, Seven Rated Critical”. No exploitation reported by Google; caveat that patches get studied by attackers.
  4. eSecurityPlanet (). “Google Chrome 157 Patches 213 Vulnerabilities, Including Seven Critical Flaws”. Corroborates 7 critical and 77 high; Google withholding some detail; no confirmed exploitation.

Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.