International
The Morning Dev

Only the news worth knowing

‹
 
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

  1. 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
YesHits tech teamsJudgment: Chrome is a browser developers and IT teams work on daily.
NoCore infrastructureJudgment: Chrome is a single vendor product, not shared core infrastructure like OpenSSH or glibc.
YesPopular toolJudgment: Chrome is one of the most widely used browsers and platforms.
NoExploited in the wildSecurityWeek: reports 204 patched vulnerabilities; no observed attacks mentioned.
NoPublic exploitSecurityWeek: reports patches and bounty payments; no published exploit mentioned.
NoRemote, no loginSecurityWeek: no details on attack vector or authentication requirements given.
NoFull takeoverSecurityWeek: no severity or impact such as code execution is described.
NoSecrets exposedSecurityWeek: reports patches and bounties; no data theft or exposure mentioned.
NoSupply chainSecurityWeek: routine Chrome 158 security patch release; no compromised channel mentioned.
NoNo fix yetSecurityWeek: Chrome 158 ships patches for 204 vulnerabilities, so fixes are available.

Timeline

  1. SecurityWeek reports that Chrome 158 patches 204 vulnerabilities

  2. SecurityWeek

    Chrome 158 Patches 204 Vulnerabilities

Source

Chrome 158 Patches 204 Vulnerabilities ↗ SecurityWeek · 2h ago

First seen · 1 source · Full story page · How tiers are decided