Finding and attribution
Crashpad accepted renderer-controlled data across the sandbox boundary without sufficient bounds checking. A renderer already compromised by an earlier stage could write outside a buffer in the out-of-sandbox handler. Google credited Brendan Dolan-Gavitt of XBOW; the XBOW account says AI agents and a human researcher built the Chrome chain together.
Product: Google Chrome for Windows (Crashpad). AI system: XBOW AI agents using OpenAI GPT-5.6 Sol and predecessors. Team / organization: XBOW and affected product vendor.
CVE identifiers: CVE-2026-78952.
AI and human contribution (source account): Google’s Chrome release note credits the XBOW researcher for this named CVE. XBOW says the broader six-day Chrome exploit chain was built with its AI agents and OpenAI GPT-5.6 Sol and predecessors. The account notes one initially considered chain bug was already known, so this record relies on the distinct CVE and vendor reporter credit and does not claim all three bugs were novel to XBOW.
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 sources establish public disclosure and correction, but do not establish whether defenders knew of the flaw before these reports.
Remediation status: fix documented. Google’s release notes and XBOW per-CVE advisory document the Chrome 152.0.7977.65 fix. The chain was reported to Google; the company says the vulnerabilities were never used against Chrome users.
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 13 Oct 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-78952: CVSS 3.1 · 8.3 (High) ·
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2026-78952: code execution.
Prerequisites / affected scope: A remote attacker must first compromise the renderer process; a crafted HTML page can then permit code execution outside the sandbox on Windows..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Google’s release notes and XBOW per-CVE advisory document the Chrome 152.0.7977.65 fix. The chain was reported to Google; the company says the vulnerabilities were never used against Chrome users.