Your web browser is probably the app you use most: for email, banking, shopping and almost every work system. That also makes it one of the most attractive targets for attackers. Google's new Chrome 157 fixes 213 security flaws, and the fix only protects you once your browser has restarted.

What happened

On 3 November 2026 Google promoted Chrome 157 to its stable channel for Windows, Mac and Linux, with the rollout continuing over the following days and weeks. The versions are 157.0.8103.38 on Linux and 157.0.8103.38/.39 on Windows and Mac.

Google's release post says the update includes 213 security fixes, and 7 of them are rated critical.

The critical flaws include buffer overflows in Dawn (Chrome's WebGPU graphics component), memory corruption in ANGLE (another graphics layer), and "use after free" bugs in WebGL, Prerender, Geometry and Core. A use-after-free bug is like a program carrying on using a storage box after handing it back: if an attacker can slip something into that box, the program may run it. Malwarebytes notes that bugs of this kind can crash the browser or, in some cases, let an attacker run code.

Google's post does not say that any of these flaws are being exploited. As usual, it keeps some bug details private until most users have updated. Several fixes are credited to researchers using AI-assisted tools, a sign of how quickly flaws are now being found.

Chrome 157 (157.0.8103.38) is also rolling out for Android through Google Play. Google says Android releases contain the same security fixes as the matching desktop release unless stated otherwise.

Microsoft Edge is built on the same Chromium code. On 3 November Microsoft's Edge security release notes said it was aware of the recent Chromium fixes and was working on a security fix. If you use Edge, check that it has updated too: Microsoft lists each Edge security release in those notes.

Why it matters

A browser processes content from anywhere on the internet. A flaw in how it handles graphics, web pages or files can, in the worst case, be triggered simply by visiting a malicious page. Once a fix is public, attackers can study the changes to work out what was broken, so the gap between release and installation is where the risk sits.

The catch is that Chrome usually downloads updates quietly but applies them only when it restarts. Many people leave their browser open for weeks, so an "updated" computer can still be running the old version.

What it means for you

At home: in Chrome on a computer, click the three-dot menu, then Help, then About Google Chrome. Chrome checks for updates; if you see Relaunch, click it. Your tabs reopen afterwards (Incognito windows do not). On Android, update Chrome from Google Play. Do the same check in any other browser you use.

If you run a small business: browsers count as software under Cyber Essentials. The NCSC's v3.3 requirements say software on in-scope devices must be licensed and supported, should have automatic updates enabled where possible, and must have updates fixing critical or high-risk vulnerabilities installed within 14 days of release. Chrome 157 is such an update. Ask staff to restart their browsers, or ask your IT provider to confirm every computer is on the new version.

If you work in IT or at an MSP:

  1. Report browser versions across all managed devices, not just whether updates are allowed.
  2. Use your management tool's browser policies to keep automatic updates on and to prompt, then force, a relaunch after an update within a set time.
  3. Track Chromium-based browsers separately: Edge and others follow Chrome's fixes on their own schedules.
  4. Remove old or unused browsers so they do not sit unpatched.

The bottom line

Chrome 157 is a large security release, with seven critical fixes. Updating is easy, but it is not finished until the browser restarts. Check the About page today, and make sure the browsers you manage really are on the new version.

This article summarises and comments on the sources listed below. It is general information, not legal or professional advice.