C21/100
Vulnerability · high
Chrome 158 patches 204 vulnerabilities
Tier C · Keep an eye on it – Check if you’re affected
Who’s exposed: Chrome users running versions before 158
Tier C because: Hits tech teams
Reach
Attack
Damage
Fix
Popular tool
What to do
- Update Chrome to version 158
The Brief
- Google's Chrome 158 release patches 204 vulnerabilities.
- Google paid $11,000 for five externally reported flaws.
- Payment amounts for 36 other bugs have not yet been determined.
Why it matters
Chrome users running versions before 158 are exposed to the fixed vulnerabilities until they update.
The checklist behind the tier
Checklist · 2 of 10 yes
| Yes | Hits tech teams | Judgment: Chrome is a browser developers and IT teams work on daily. |
| No | Core infrastructure | Judgment: Chrome is a single vendor product, not shared core infrastructure like OpenSSH or glibc. |
| Yes | Popular tool | Judgment: Chrome is one of the most widely used browsers and platforms. |
| No | Exploited in the wild | SecurityWeek: reports 204 patched vulnerabilities; no observed attacks mentioned. |
| No | Public exploit | SecurityWeek: reports patches and bounty payments; no published exploit mentioned. |
| No | Remote, no login | SecurityWeek: no details on attack vector or authentication requirements given. |
| No | Full takeover | SecurityWeek: no severity or impact such as code execution is described. |
| No | Secrets exposed | SecurityWeek: reports patches and bounties; no data theft or exposure mentioned. |
| No | Supply chain | SecurityWeek: routine Chrome 158 security patch release; no compromised channel mentioned. |
| No | No fix yet | SecurityWeek: Chrome 158 ships patches for 204 vulnerabilities, so fixes are available. |
Timeline
Source
Chrome 158 Patches 204 Vulnerabilities ↗ SecurityWeek · 2h ago
First seen · 1 source · Full story page · How tiers are decided