vulns.co
/
GKData.io MCP and API Buy me a coffee

Google · Memory safety and parser contracts

V8 control-flow analysis omitted required initialization checks

V8 removed an initialization check without ensuring that it was safe to do so on every code path. The report demonstrated memory corruption inside a sandboxed renderer, not a sandbox escape or full-machine compromise. Google confirms a USD 50,000 award for this distinct report.

Read the original writeupUSD 50,000 reported award · Reviewed 2026-10-02

Root cause

Control-flow analysis treated an initialization safety check as redundant without preserving its guarantee across every incoming path.

Demonstrated impact

The report demonstrated sandboxed renderer memory corruption. A sandbox escape or full-machine compromise is not established.

What to check for

  • Check-removal optimizations must preserve initialization guarantees across all control-flow paths.
  • Separate a compiler fix, stable-release availability and public report access in remediation records.

Award and evidence

USD 50,000Bug Bounty · Vendor Confirmed
How the award was verified, and what the record does not establish

Panel decision and tracker reward metadata identify one report. Dollar notation uses official Chromium USD context. Cash receipt is unverified.

  • Payment completion is unverified; USD relies on official program context.
  • Issue dates follow displayed calendar dates; timestamp timezone was not established.
  • Release page was corrected November 17 to add other CVEs. This entry remains in the original main list.

Timeline

Published
2026-01-22explicit · Comment #24 records removal of issue access restrictions.
Public Disclosure
2025-10-28explicit · Vendor advisory preceded full issue access.
Reported
2025-10-10explicit
Awarded
2025-10-17explicit
Fixed
2025-10-28explicit · Stable release announced staged rollout; main fix recorded October 10 and Fixed status October 15.
Award Announced
2025-10-28explicit · Listed in the dated release notice; no original-page snapshot reviewed.

Related cases

All 10 cases in Memory safety and parser contracts

Sources

  1. Chromium issue 450618029Google Chromium security team · reviewed 2026-10-02
  2. Chrome Stable Channel Update for Desktop, 2025-10-28Google Chrome team · reviewed 2026-10-02
  3. Security rewards at Google: Two MEEELLION Dollars LaterChromium team · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software