Google has released Chrome version 158, patching 204 security vulnerabilities. The update includes fixes for 163 flaws discovered by researchers, with 145 attributed to Xinyang Ge and 15 to Google’s internal team.
Key Vulnerabilities Patched
Use-after-free flaws are the most common, with 51 instances. These occur when memory is accessed after it’s been freed, allowing attackers to run arbitrary code without user action.
- Three critical use-after-free issues affect WebView, GarbageCollection, and WebAudio—core components for web content and media playback.
- Out-of-bounds write defects in GPU and ANGLE could cause memory corruption, leading to privilege escalation or denial-of-service.
- A buffer overflow in the Media module poses a risk during media playback, allowing malicious payloads to be injected.
- Incorrect and missing authorization flaws weaken access controls, possibly exposing user profiles or private data.
Security Rewards and Payments
Google paid $11,000 in bug bounty rewards for five vulnerabilities reported by external researchers.
The team says this decision is based on exploitability and impact assessments.
One researcher noted the lack of rewards may reflect a policy, not a technical judgment. ‘Transparency on reward decisions is essential,’ they said.
Update Availability
Chrome 158 is rolling out automatically. Users on Windows, macOS, and Linux will receive the update through Chrome’s update channels.
Background: How Vulnerabilities Are Discovered and Patched
Google’s security team, including Project Zero, finds and reviews vulnerabilities through public reports and internal testing.
Flaws are assessed for severity, exploitability, and real-world impact before a patch is assigned. The process can take weeks or months.
Google often does not disclose reward amounts, especially for flaws not exploited in the wild or with limited impact. This may reduce motivation for researchers.
Why This Matters
The update fixes many flaws.
Researchers rely on financial incentives to fund their work. Without clear reward policies, future reporting may decline.
Limitations and Open Questions
There is no evidence any of the vulnerabilities have been exploited in real attacks.
Google has not specified how many flaws were found by external researchers versus internal teams. This detail is missing.
Reasons for no rewards may include low impact, limited exploitability, or internal policy. Users should update immediately.
For more details, see the original report at SecurityWeek.
Related coverage includes critical vulnerabilities in Perforce Puppet and Oracle’s November 2026 CSPU.
Sources & further reading
Featured image: Chrome security. Via original publisher. Image source
