Full Report
A team at security firm XBOW chained three then-unknown Google Chrome bugs into a single attack that runs code on a Windows computer when the user only loads a web page, the company said. Its researchers built the attack in six days by directing AI agents running OpenAI's publicly available GPT-5.6 Sol model. Google has since confirmed all three bugs, fixed them, and paid XBOW its top $
Analysis Summary
# Vulnerability: Chrome Full-Chain Exploit (V8, WebP, and Crashpad)
## CVE Details
- **CVE ID:**
- CVE-2026-85045 (V8 JavaScript Engine)
- CVE-2026-78952 (Crashpad)
- *Note: A third bug in the Animated-WebP decoder was fixed but lacks a specific public identifier in the source.*
- **CVSS Score:** Not explicitly listed, but rated as **High** severity by Google.
- **CWE:**
- V8: Memory Corruption / Out-of-bounds access
- WebP: Out-of-bounds Write
- Crashpad: Sandbox Escape / Logic Flaw
## Affected Systems
- **Products:** Google Chrome / Chromium-based browsers.
- **Versions:** Versions prior to 152.0.7977.82.
- **Configurations:** Windows operating systems (specifically targeted in this exploit chain).
## Vulnerability Description
This vulnerability involves a "full-chain" exploit composed of three distinct flaws that bypass all layers of Chrome's security:
1. **Stage 1 (V8 Engine):** A memory corruption flaw in the JavaScript engine allowed for initial memory control within the browser process.
2. **Stage 2 (WebP Decoder):** A flaw in the Animated-WebP image decoder used the V8 memory control to escape the inner sandbox and perform a precise memory write.
3. **Stage 3 (Crashpad):** A flaw in Chrome’s crash handler (which resides outside the primary sandbox) converted the memory write into arbitrary code execution on the host Windows machine.
## Exploitation
- **Status:** PoC available (Developed by XBOW researchers using AI agents). No evidence of exploitation in the wild.
- **Complexity:** High (Requires chaining three distinct vulnerabilities).
- **Attack Vector:** Network (Remote). The attack is triggered when a user simply loads a malicious web page ("Zero-click" once the page is navigated to).
## Impact
- **Confidentiality:** High (Full code execution on the host machine).
- **Integrity:** High (Ability to modify files and system settings).
- **Availability:** High (Ability to crash the system or take control of resources).
## Remediation
### Patches
- **Google Chrome 152.0.7977.65:** Fixed the Crashpad vulnerability (Aug 25, 2026).
- **Google Chrome 152.0.7977.82:** Fixed the V8 engine vulnerability (Sep 3, 2026).
- Users must update to version **152.0.7977.82 or later**.
### Workarounds
- No specific workarounds provided. Users are advised to enable automatic updates and ensure the browser is restarted to apply fixes.
## Detection
- **Indicators of Compromise:** Unusual outbound network traffic from the Chrome process; crashes in `crashpad_handler.exe` followed by unauthorized PowerShell or CMD execution.
- **Detection methods and tools:** EDR (Endpoint Detection and Response) tools should monitor for Chrome child processes that bypass sandbox restrictions or attempt to write to sensitive memory regions.
## References
- Google Chrome Release Blog: [https://chromereleases.googleblog[.]com/2026/08/stable-channel-update-for-desktop_0256176589.html]
- CVE Repository (V8): [https://www.cve[.]org/CVERecord?id=CVE-2026-85045]
- CVE Repository (Crashpad): [https://www.cve[.]org/CVERecord?id=CVE-2026-78952]
- Chromium Security VRP: [https://chromium.googlesource[.]com/chromium/src/+/main/docs/security/vrp-faq.md]