SamoTech

TECHNOLOGY • APPS • IDEAS

SamoTech / Chrome 157 and Firefox 160 Patch Over 180 Bugs: Why Use-After-Free Keeps Topping the List and What to Do

Chrome 157 and Firefox 160 Patch Over 180 Bugs: Why Use-After-Free Keeps Topping the List and What to Do

Browser security

Your browser updated itself twice this week, or it is about to. Between them, Chrome 157 and Firefox 160 fixed more than 180 security bugs. The number is big, but the pattern inside it is more useful than the total.

The numbers, from the sources

Google's Chrome Releases notice for the November 11, 2026 stable update says it includes 83 security fixes and moves Chrome to 157.0.8103.78/.79 on Windows and Mac and 157.0.8103.78 on Linux, rolling out over the coming days and weeks. SecurityWeek (November 12) breaks the batch down:

  • Five critical bugs, all use-after-free, in ServiceWorker, CSS, Layout, Skia and Accessibility.
  • 78 high-severity bugs, mostly use-after-free (24), out-of-bounds read or write (10), type confusion (9), uninitialized resource (9) and incorrect or missing authorization (8).
  • Google found 52 of the bugs internally, and researchers from Anthropic and OpenAI reported 18 more.

On the Mozilla side, SecurityWeek says Firefox 160 patched 99 vulnerabilities, 57 of them high severity, mostly use-after-free, incorrect boundary and sandbox escape issues. Mozilla also shipped fixes in Thunderbird 160 and several Firefox ESR releases. SecurityWeek adds that neither Google nor Mozilla mentions exploitation in the wild for these bugs.

Why use-after-free keeps winning

A use-after-free bug happens when a program keeps using a piece of memory after it has been released. If an attacker can influence what gets placed in that memory next, the program may crash, corrupt data or, in the worst case, run attacker-controlled code, as Cyber Security News explains.

The Chrome notice also tells you how such bugs are found. It says many security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer or AFL. These are testing tools that catch memory errors while the code runs on many unusual inputs.

Comparison: what the two projects tell you

  • Same enemy, same shape. Both reports lead with use-after-free. Different codebases, similar failure mode.
  • Different layers. Chrome's critical bugs sit in components like ServiceWorker, CSS and Skia. Firefox's list includes sandbox escape and same-origin policy bypass bugs.
  • Credit lines changed. Chrome's notice credits several reports to researchers "assisted by Claude" and one to OpenAI Codex Security. That is the notice's wording, and it shows AI-assisted bug hunting is now part of the normal disclosure flow.

A practical example: updating without guessing

Securityonline's guidance for Chrome is to open Settings, then About Chrome, let the update download, and click Relaunch. It matters because the rollout takes days or weeks, so waiting may leave you on the old version. Securityonline says the Relaunch step is what applies the update. To check Chrome, compare the version on that page with 157.0.8103.78 or later, noting the Windows and Mac build ends in .78 or .79. Other Chromium-based browsers need their own vendor's update.

Not the only Chrome fix this week

Two days earlier, on November 9, Google shipped Chrome 157.0.8103.50/.51 with nine security fixes, including CVE-2026-125350, a high-severity use-after-free in Chrome's XML component that Google said has an exploit in the wild, according to Malwarebytes and an alert from NHS England Digital. The later .78 build is the one to be on.

What this means

Treat the browser update as a habit, not an event. The practical rule is simple: install the update, restart the browser, and do not postpone the restart for days. The large counts are not a sign of active attacks: the sources report no exploitation for these bugs, and Google says it found 52 of the Chrome bugs itself.

What is not known

Google restricts bug details until most users are updated, so we do not know how any of these bugs could be exploited. The sources do not report which of the Chrome fixes ship to Android in the same form, and we did not install or test either browser.

Sources: Google Chrome Releases, "Stable Channel Update for Desktop" (November 11, 2026, chromereleases.googleblog.com); SecurityWeek, "Chrome, Firefox Updates Patch Over 180 Vulnerabilities" (November 12, 2026, securityweek.com); Malwarebytes, "Update Chrome now to fix a flaw attackers are exploiting" (November 10, 2026, malwarebytes.com); NHS England Digital cyber alert (November 10, 2026, digital.nhs.uk); Securityonline and Cyber Security News coverage of the Chrome 157 update (November 12, 2026). Read November 16, 2026. This is a summary and analysis of those reports.

Join the discussion on Blogger