Home / Blog / Chrome 158 Patches 204 Vulnerabilities: Google handed out…
Tech News

Chrome 158 Patches 204 Vulnerabilities: Google handed out $11,000 for five

Google released Chrome 158 with patches for 204 vulnerabilities, paying $11,000 for five flaws while addressing six critical bugs across graphics and media.

By Dillip Chowdary • Nov 18, 2026 • Source: SecurityWeek

Chrome 158 Patches 204 Vulnerabilities: Google handed out $11,000 for five
Image: SecurityWeek

At a glance

Product
Google Chrome
Version
158.0.8127.36/.37
Release date
Tuesday
Total vulnerabilities
204 patches
Critical flaws
6 bugs resolved
Bounty payout
$11,000 paid for 5 flaws

Google launched Chrome 158 to the stable channel on Tuesday, deploying patches for 204 security vulnerabilities across its browser architecture. The update resolves multiple memory flaws, which SecurityWeek's report notes includes six critical-severity defects in core subsystems. Google confirmed that 163 of the resolved weaknesses will receive no bounty payout.

This report outlines the full security release for enterprise administrators, security engineers, and desktop users maintaining Chromium browser installations. It covers the complete vulnerability breakdown, internal discovery efforts, memory corruption flaws, bounty reward distributions, and platform rollout builds across supported operating systems.

01Six critical defects in core browser engines

The critical vulnerabilities resolved in this milestone impact components handling graphics rendering, garbage collection, and audio processing. Three of the six critical flaws consist of use-after-free bugs discovered in WebView, GarbageCollection, and the WebAudio framework. These defects expose the browser runtime to unsafe memory reuse when dynamically allocated objects are freed.

Beyond the audio and garbage collection issues, the browser received patches for two out-of-bounds write bugs in the GPU and ANGLE graphics subsystems. The engineering team also resolved a critical buffer overflow vulnerability within the Media pipeline. Memory corruption errors in rendering and media components present serious integrity hazards if triggered by untrusted content.

Google confirmed that no bug bounty rewards will be paid for any of the six critical vulnerabilities resolved in this release. All six issues were surfaced through internal research pipelines and code auditing rather than external disclosures. Because these findings originated internally, none qualified for financial compensation through Google public reward program.

02Internal bug discoveries and external bounty payouts

Internal researchers accounted for the vast majority of the security weaknesses uncovered and patched in this browser release. Google internal staff identified 145 separate vulnerabilities, while security researcher Xinyang Ge discovered another 15 distinct bugs. In total, 163 of the 204 resolved security weaknesses will receive no monetary reward under program guidelines.

For qualifying external submissions, Google distributed $11,000 in bug bounty rewards across five evaluated security flaws. However, reward review committees have yet to determine the bounty amounts to be disbursed for 36 remaining externally reported issues. Total compensation figures for this milestone will rise once maintainers finish evaluating the technical impact of those submissions.

This split payout structure demonstrates Google practice of shipping security patches immediately rather than waiting for bounty committees to calculate financial awards. External researchers who submitted the 36 pending bugs will receive payments based on severity, exploitability, and report quality. Meanwhile, browser users receive the security fixes without waiting for reward administration to conclude.

03Severity breakdown across two hundred security issues

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

The 204 patched vulnerabilities are distributed across four distinct severity tiers established under Google security taxonomy. In addition to the six critical flaws, the release incorporates patches for 62 high-severity issues affecting diverse browser operations. High-severity bugs typically involve elevated security risks such as potential privilege boundary violations or sandbox circumvention under specific conditions.

Medium-severity flaws formed the single largest group in this update, with 82 separate defects remediated throughout the codebase. The development team also patched 54 low-severity vulnerabilities, which address minor weaknesses and limited logic inconsistencies. Combined, medium and low-severity vulnerabilities account for 136 of the total issues addressed in the release.

Severity LevelVulnerability CountReward Status
Critical6No bounty rewards paid
High62Included in paid and pending pool
Medium82Included in paid and pending pool
Low54Included in paid and pending pool
Total204163 unpaid, 5 paid, 36 pending

This structured classification enables security teams to evaluate the exposure profile across managed enterprise browser deployments. By quantifying vulnerabilities across clear severity boundaries, administrators can prioritize endpoint updating schedules based on potential impact. Resolving 68 critical and high vulnerabilities simultaneously delivers immediate defensive hardening for all client installations.

04Memory safety flaws and authorization weaknesses

Memory corruption vulnerabilities represented the most prevalent bug category patched in Chrome 158, led by 51 distinct use-after-free defects. Additionally, the patch set repaired 15 out-of-bounds write and read errors, alongside 14 uninitialized resource flaws. Together, these memory safety issues total 80 distinct weaknesses capable of causing application crashes or memory corruption during browser operations.

Authorization defects represented the second largest category of security weaknesses resolved by browser engineers. The update remediates 34 instances of incorrect authorization and 16 cases of missing authorization checks across components. These 50 combined authorization vulnerabilities address logical deficiencies where internal mechanisms failed to validate permissions properly before executing privileged actions.

Other vulnerability classes remediated in this release include 11 information leaks, 10 user interface misrepresentations, nine improper input validation defects, and eight race conditions. Fixing interface misrepresentations ensures malicious web content cannot disguise origins or display deceptive navigation indicators to users. Correcting input validation flaws and race conditions prevents unexpected execution states when the browser handles asynchronous network events.

05Platform release versions and desktop update schedule

Google confirmed that none of the 204 vulnerabilities patched in this release are known to be exploited in the wild. While active attacks have not been detected, security teams advise all users to apply the security update promptly. Applying fixes quickly closes exposed attack surfaces before proof-of-concept exploits can be developed from public patch diffs.

The stable channel release is currently deploying across all desktop platforms via standard distribution channels. For Windows and macOS operating systems, the updated browser rolls out as versions 158.0.8127.36 and 158.0.8127.37. Linux installations will receive the patched browser build designated as version 158.0.8127.36 across software repositories.

Note: Desktop installations will receive these security builds automatically through the browser background update mechanism. Users can accelerate the update process by navigating directly to the browser help menu to initiate an immediate version check. Relaunching the application is required to finalize installation and replace running binary components.

Frequently asked questions

How many security vulnerabilities were patched in Chrome 158?

Google patched 204 vulnerabilities in Chrome 158, comprising six critical flaws, 62 high-severity issues, 82 medium-severity bugs, and 54 low-severity weaknesses.

Have any of the vulnerabilities in Chrome 158 been exploited in the wild?

Google made no mention of any patched vulnerabilities being exploited in the wild. Even so, users are advised to update their browsers as soon as possible.

What are the version numbers for the Chrome 158 release?

The release rolls out as versions 158.0.8127.36 and 158.0.8127.37 for Windows and macOS, and as version 158.0.8127.36 for Linux systems.

How much bug bounty money did Google pay out for Chrome 158?

Google paid $11,000 for five externally reported flaws and has yet to determine amounts for 36 bugs. No bounty rewards were paid for 163 weaknesses.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →