Full Report
Xbow earned a $250K bug bounty and all the AI model got was a lousy t-shirt
Analysis Summary
# Vulnerability: AI-Assisted Chrome Full-Chain Sandbox Escape
## CVE Details
* **CVE ID:**
* **CVE-2026-X1** (V8 Maglev Compiler Bug - Tracker: 547819997)
* **CVE-2026-X2** (Blink/WebP Sandbox Escape - Tracker: 536913431)
* **CVE-2026-X3** (Crashpad Memory Safety Bug - Tracker: 545820931)
* **CVSS Score:** 10.0 (Critical - based on full-chain impact)
* **CWE:** CWE-822 (Untrusted Pointer Dereference), CWE-787 (Out-of-bounds Write), CWE-119 (Memory Corruption)
## Affected Systems
* **Products:** Google Chrome Browser
* **Versions:** All versions prior to 152.0.7977.82
* **Configurations:** Specifically impacts Chrome running on Windows operating systems.
## Vulnerability Description
This exploit represents a "full-chain" attack involving three distinct stages to bypass multiple security layers:
1. **Maglev Compiler Flaw:** A vulnerability in V8's mid-tier compiler caused by the reuse of a mutable boxed number during deoptimization. This allows an attacker to achieve read/write access within the V8 pointer-compression cage.
2. **V8 Sandbox Escape:** Exploitation of an animated-WebP decoder bug. This leverages a property that the Blink rendering engine incorrectly assumed was trusted, allowing the attacker to escape the V8-specific memory sandbox.
3. **Process Sandbox Escape (Crashpad):** A memory-safety overflow vulnerability in Crashpad (Chrome's crash reporting system). This allows the attacker to break out of the final outer OS-level process sandbox.
## Exploitation
* **Status:** PoC developed by researchers; fixed by vendor. While not currently reported in the wild, the use of LLMs (GPT-5.6 Sol) reduced the discovery and development time from months to six days.
* **Complexity:** Medium (Requires chaining three specific vulnerabilities, though AI assistance significantly lowers the barrier).
* **Attack Vector:** Network (Remote via malicious website).
## Impact
* **Confidentiality:** Total (Full access to host machine data).
* **Integrity:** Total (Execution of native code outside the browser sandbox).
* **Availability:** Total (Ability to crash the system or take full control).
## Remediation
### Patches
* **Google Chrome:** Update to version **152.0.7977.82** or later.
* Users must **relaunch the browser** for the updates to take effect.
### Workarounds
* None provided. Immediate patching is the only recommended course of action due to the nature of remote code execution.
## Detection
* **Indicators of Compromise:** Unusual Crashpad activity or unexpected child processes spawned by `chrome.exe`.
* **Detection Methods:** Monitor for heap spray patterns or anomalous memory access within the Chrome renderer process. Enterprise security suites should flag attempts by the browser to execute native code outside of its standard sandboxed environment.
## References
* Xbow Research Blog: hxxps[://]xbow[.]com/labs/research/zero-to-calc-in-six-days-inside-xbow-chrome-full-chain
* V8 Sandbox Technical Documentation: hxxps[://]v8[.]dev/blog/sandbox
* Chromium Issue Tracker:
* hxxps[://]issues[.]chromium[.]org/issues/547819997
* hxxps[://]issues[.]chromium[.]org/issues/536913431
* hxxps[://]issues[.]chromium[.]org/issues/545820931