AI Science Tracker

Google Big Sleep is credited for a Chrome WebPackaging use-after-free

Google Chrome (WebPackaging) · AI involvement attributed to Google Big Sleep

Finding and attribution

Google's Chrome stable release note identifies a WebPackaging flaw as high severity and lists the stable build containing the fix.

Product: Google Chrome (WebPackaging). AI system: Google Big Sleep. Team / organization: Google.

CVE identifiers: CVE-2026-87639.

AI and human contribution (source account): Google's per-CVE Chrome stable release note identifies Google BigSleep@Grape as the reporter on August 5, 2026. The note does not describe the agent's analysis steps or the extent of human review.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The cited stable release documents the issue and fix; it makes no claim that this CVE was exploited in the wild.

Remediation status: fix documented. Google lists Chrome 153.0.8010.36/.37 for Windows/Mac and .36 for Linux. as the release containing the fix. This does not establish installation or deployment on any device.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 8 Sep 2026. AI attribution dated 8 Sep 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 8.3. Documented technical effects: code execution.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-87639: code execution.
Prerequisites / affected scope: A remote attacker must first compromise the Chrome renderer; a crafted HTML page may then permit arbitrary code execution outside the sandbox..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: Google lists Chrome 153.0.8010.36/.37 for Windows/Mac and .36 for Linux. as the release containing the fix. This does not establish installation or deployment on any device.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases