Skip to content
Security & Trust

Chrome 158 fixes 204 flaws, and most were found by Google itself

The size of the patch matters less than how quickly it reaches every laptop in your company

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
Chrome 158 fixes 204 flaws, and most were found by Google itself
In brief
  • Google released Chrome 158 with fixes for 204 vulnerabilities, six of them critical, according to SecurityWeek's report on the announcement.
  • Google and a researcher named Xinyang Ge found 160 of the flaws, and no reward will be paid for them. SecurityWeek says Google mentions no exploitation in the wild.
  • The work for organisations is fleet-wide: confirm every managed desktop reaches version 158.0.8127.36 or later, and check which devices lag.

A big patch can mean a working process

A release with 204 security fixes sounds like an emergency. The reported facts point somewhere calmer. Google's stable-channel update for Chrome 158, as SecurityWeek describes it, carries 204 security fixes. SecurityWeek also notes that Google does not mention exploitation in the wild for any of them.

That is our interpretation, not SecurityWeek's. A large number of fixes can mean a large amount of looking. SecurityWeek says Google and a researcher named Xinyang Ge discovered 145 and 15 of the flaws, respectively. Google's silence on exploitation is not proof that none occurred, but it is the only signal the report gives.

The risk for your organisation is not in the count. It is in the gap between the day a fix exists and the day it reaches every machine.

What was fixed

SecurityWeek lists six critical-severity bugs. Memory-handling faults make up five of them. The affected components are WebView, GarbageCollection and WebAudio (each a use-after-free), GPU and ANGLE (each an out-of-bounds write). The sixth is a buffer overflow in Media.

These terms describe memory mistakes. A use-after-free happens when a program keeps using a piece of memory after it has handed it back. An out-of-bounds write puts data outside the space set aside for it. In a browser, such errors can let a crafted web page interfere with the program that opens it.

The rest of the list, per SecurityWeek, is 62 high-severity flaws, 82 medium and 54 low. These add up to 204 with the six critical ones.

The pattern inside the list

SecurityWeek lists the most common flaw types. Use-after-free leads with 51 occurrences, about a quarter of the 204. Next come incorrect authorization (34) and missing authorization (16). Out-of-bounds write or read follows with 15, uninitialized resource with 14, and information leak with 11.

Add the two authorization categories together and you get 50 flaws. That is our arithmetic on SecurityWeek's figures, not a number the report gives. It is worth a look because authorization flaws are not memory errors. They are failures to check whether an action is permitted.

One release is one data point. It does not show a trend. It does show that a modern browser's risk is not only about memory bugs. It also includes whether the software asks the right question before it acts.

Who gets paid, and who does not

The reward figures show how the work is split. SecurityWeek says no bounty will be paid for 163 of the flaws. Google says it paid $11,000 for five reports from external researchers and has yet to decide amounts for 36 others.

So 41 of the 204 carry rewards, paid or pending. Google's and Ge's 160 account for most of the 163 with no reward. SecurityWeek does not explain the other three.

What to ask your team

The update is reaching users as versions 158.0.8127.36 and .37 on Windows and macOS, and 158.0.8127.36 on Linux, SecurityWeek says. It also reports that users are advised to update as soon as possible.

Put four questions to your IT lead. How many managed desktops run Chrome? How many are on version 158.0.8127.36 or later today? Which devices cannot restart the browser without help, such as shared kiosks and call-centre seats? Who owns Chrome on contractors' laptops?

The answers are a measure of how well you control your own endpoints. A browser fix that exists on Google's servers protects no one until it runs on your staff's machines.

The count says little about your exposure. How long your slowest laptop takes to update says a great deal.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Google.