AI Science Tracker

Google Chrome V8 TurboFan load-elimination stale property storage

Google Chrome / V8 · AI involvement attributed to depthfirst dfs-large1

Finding and attribution

A migration-capable map check can replace an object’s property storage, but TurboFan load elimination retains the old property-array pointer and uses it with the new layout. The article says this memory-corruption entry bug was combined with a separate shared-Wasm sandbox-escape issue to achieve renderer code execution; this record does not attribute that separate escape to this CVE.

Product: Google Chrome / V8. AI system: depthfirst dfs-large1. Team / organization: depthfirst / Google Chrome security team.

CVE identifiers: CVE-2026-79236.

AI and human contribution (source account): depthfirst’s primary technical account expressly states it used dfs-large1 to uncover CVE-2026-79236 and describes its specific root cause. The author says the research system found and validated the issue; the article documents manual exploit development and human investigation separately. The Chrome CNA record independently confirms the CVE, affected release boundary and severity. The article’s exploit chain uses this bug together with a separate V8 sandbox-escape issue; the separate issue is not included in this CVE record.

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 Chrome CNA record was published 2026-08-25; the depthfirst technical account was published 2026-10-20. The article describes an exploit chain, but no checked source reports exploitation in the wild or establishes zero-day status.

Remediation status: fix documented. The Chrome CNA record lists versions before 152.0.7977.65 as affected and 152.0.7977.65 as the fixed boundary. The depthfirst account says the V8 change was marked fixed upstream on 2026-08-20. This does not establish installation-level patch state.

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 25 Aug 2026. AI attribution dated 20 Oct 2026. Sources checked 17 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-79236: code execution.
Prerequisites / affected scope: A remote attacker supplies a crafted HTML page and a user interacts with it. The Chrome CNA says arbitrary code execution inside the browser sandbox; depthfirst says its demonstrated renderer/native-code chain combined this memory-corruption CVE with a separately tracked shared-WebAssembly sandbox-escape issue. The escape itself is outside this record..
Exploitation evidence: The cited sources describe research and a constructed exploit chain. They do not report exploitation in the wild.. Impact source · checked 17 Nov 2026.

Documented fix: The Chrome CNA record lists versions before 152.0.7977.65 as affected and 152.0.7977.65 as the fixed boundary. The depthfirst account says the V8 change was marked fixed upstream on 2026-08-20. This does not establish installation-level patch state.

Original evidence

Download this source record (JSON)

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