AI Science Tracker

Google Big Sleep and Grape discover a Blink QualifiedName use-after-free

Google Chrome (Blink DOM Sanitizer) · AI involvement attributed to Google Project Big Sleep with Grape variant-analysis mode

Finding and attribution

A web worker could invoke an experimental Trusted Types parser-options API and concurrently mutate a process-global QualifiedName cache that was designed for main-thread access, causing a heap use-after-free. The issue affected an experimental, not-yet-shipped feature at the time of discovery.

Product: Google Chrome (Blink DOM Sanitizer). AI system: Google Project Big Sleep with Grape variant-analysis mode. Team / organization: Google Project Zero / Google Chrome.

CVE identifiers: CVE-2026-76021.

AI and human contribution (source account): The Chromium vulnerability report calls this “a discovery of Project BigSleep (w/ Grape, a variant analysis mode)” and its issue metadata credits Google BigSleep@Grape. A later comment describes a researcher working with the Big Sleep team; the public evidence therefore supports collaborative AI-assisted discovery, not an autonomous-agent-only claim.

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: Google’s release note and issue record establish a fix and disclosure but do not assert in-the-wild exploitation.

Remediation status: fix documented. Google’s Chrome update fixed the issue in version 151.0.7922.173. The Chromium report says the trigger used an experimental feature not yet shipped at discovery; do not assume it was available to ordinary stable users then. Device update state is not checked.

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 19 Aug 2026. AI attribution dated 19 Aug 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 8.8. 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-76021: code execution.
Prerequisites / affected scope: A remote attacker supplies a crafted HTML page; arbitrary code execution is inside the browser sandbox..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: Google’s Chrome update fixed the issue in version 151.0.7922.173. The Chromium report says the trigger used an experimental feature not yet shipped at discovery; do not assume it was available to ordinary stable users then. Device update state is not checked.

Original evidence

Download this source record (JSON)

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