XBOW’s GPT-5.6 Sol agents build a $250k Chrome full-chain exploit in six days
Confirmed
The takeaway
Google paid its first $250,000 full-chain reward under the 2026 VRP rules; all three bugs are fixed.
Status
- Claim
Confirmed
- Our reporting
- High confidence
- Importance
- 3 of 5
- Last verified
- 14 October 2026
Your AI and this story
- GPT-6 Astra166 days after its cutoff
- Claude Opus 5.5105 days after its cutoff
- Gemini 4 Argon196 days after its cutoff
- Grok 4.7135 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 105 days before it.
Key facts
- Reward: ‘the first $250,000 Chrome full-chain reward under the VRP rules introduced in April 2026’; Google confirmed the chain launched Calculator (XBOW Labs)
- Bugs: (1) V8 Maglev reused a mutable boxed number during deoptimization → read/write in V8’s pointer-compression cage (Chromium issue 547819997); (2) Blink animated-WebP decoder → one native write outside the cage (issue 548509153); (3) Crashpad trusted a failed read from a ‘frozen’ renderer → heap overflow and code execution in the crash handler (issue 545820931). All three fixed; no CVE ids given
- Time and cost: built Aug 2–7, 2026 (during Black Hat week) by Brendan Dolan-Gavitt, Andres Luksenberg, Baul Lee and Willem Pinckaers; about $40,000 of API charges, reconstructed from archived Codex logs. XBOW estimates a pre-LLM full chain at 6–9 months for a team of four; its own first Chrome full chain took about 2 months
- Model: OpenAI’s publicly available gpt-5.6-sol (and predecessors), chosen deliberately instead of a restricted cyber model such as Mythos
- Division of labour: agents searched source, tested hypotheses, built proofs of concept and exploit stages in parallel campaigns; humans chose targets, supplied context, challenged results and decided what to combine
- Duplicate collision: a first version’s Gin-based V8 sandbox escape duplicated a bug Google already knew (issue 542670566) and was replaced with the WebP stage within hours
- CEO Oege de Moor: ‘For the first time ever, defenders have access to the skills of attackers at the click of a button’; he expects agents working alone to find each of the three bugs within a year. Orchestration details due at the Unprompted conference at the end of October
What happened
XBOW, an AI offensive-security company, set its team the goal of a Chrome full chain at the start of 2026. During Black Hat week in August four researchers ran parallel agent campaigns on OpenAI’s public GPT-5.6 Sol and assembled a three-stage chain from a web page to code execution outside Chrome’s sandbox on Windows. After Google fixed the bugs, XBOW published the details on Oct 13.
Some coverage says XBOW has two more exploits under Google review; XBOW’s own posts do not say so, so it is unverified here.
Why it matters
A Chrome full chain used to take an expert team months. Here it took six days and about $40,000 of a public model’s API time, with humans steering. That is concrete evidence that frontier-model exploit capability is already in non-restricted models.
Sources
5 sources from 4 sites. Numbers match the chips in the text.
5 sources: 2 primary, 3 press
Primary
- XBOW (Oege de Moor): XBOW built a Chrome full-chain exploit (Oct 13)xbow.com, official
- XBOW Labs (Brendan Dolan-Gavitt): Zero to Calc in Six Days: Inside XBOW’s Chrome Full Chainxbow.com, official
Press
- Forbes: It cost $40,000 to find a Google Chrome zero-day bug with AI (Oct 13)forbes.com, press
- Startup Fortune: XBOW researchers used AI agents to win a $250,000 Chrome exploit bountystartupfortune.com, press
- Runtime Wire: XBOW earns Google’s $250,000 bounty with a six-day Chrome exploitruntimewire.com, press
Changes
- Filed (Google News: Startup Fortune)