The short version
- The release. Google has pushed Chrome 158 to the stable channel with fixes for 204 vulnerabilities. Six of the flaws are rated critical.
- The critical flaws. They include three use-after-free bugs, in WebView, GarbageCollection and WebAudio, out-of-bounds write defects in GPU and ANGLE, and a buffer overflow in Media.
- The severity mix. Beyond the six critical issues, the release covers 62 high-severity, 82 medium-severity and 54 low-severity vulnerabilities.
- Rewards. No bounty will be paid for the critical flaws, and 163 of the 204 carry no reward. Google says it paid $11,000 for five externally reported bugs and has not yet set amounts for 36.
- Exploitation. Google makes no mention of any of the vulnerabilities being exploited in the wild. It advises users to update as soon as possible.
What the update fixes
Chrome 158 patches 204 vulnerabilities. Six are critical: use-after-free flaws in WebView, GarbageCollection and WebAudio, out-of-bounds write defects in GPU and ANGLE, and a buffer overflow in Media.
By category, use-after-free is the most frequent fix, at 51 occurrences. It is followed by incorrect authorisation (34), missing authorisation (16), out-of-bounds write and read (15), uninitialised resource (14), information leak (11), UI misrepresentation (10), improper input validation (9) and race condition (8).
Severity and bounty decisions
Of the 204 flaws, 62 are high severity, 82 medium and 54 low. Google says it and researcher Xinyang Ge found 145 and 15 of the weaknesses respectively. The report does not break down which bugs each platform build contains.
Google is not paying a bounty for any of the six critical flaws, and 163 of the total carry no reward. It handed out $11,000 across five vulnerabilities reported by external researchers and has yet to determine amounts for 36 more.
Who is affected and what to do
Anyone running an unpatched Chrome installation is exposed to whatever the fixed flaws allow, though Google has said nothing about attacks using them. The release is rolling out as 158.0.8127.36/.37 on Windows and macOS and as 158.0.8127.36 on Linux.
The article carries no exploitation report and no advisory beyond Google's own release notes, so the practical exposure depends on how quickly browsers in an organisation are updated. Google's guidance is to update as soon as possible.
What is not known yet
- Whether any of the 204 vulnerabilities is being exploited; Google's announcement does not address the question.
- Which of the critical flaws affect which platforms, and whether the Windows, macOS and Linux builds differ in exposure.
- Whether the 36 vulnerabilities with undetermined reward amounts were reported by external researchers.
- Whether other browsers built on the same engine will ship equivalent fixes, and when.
- How long managed and deferred-update installations will remain on older versions.
What to do
If you use Chrome
- Apply the pending browser update and restart Chrome so it takes effect.
- Confirm the installed version is 158.0.8127.36 or later in the browser's settings page.
If you manage browsers for an organisation
- Push the update through your endpoint or browser management tooling rather than waiting for users to act.
- Check for devices or policies that defer browser updates and shorten the deferral.
For everyone else
- Leave automatic browser updates switched on.
- Restart the browser when an update is offered instead of postponing it.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.