XBOW's AI built a Chrome exploit for $40K. Relaunch your browsers

An AI-built Chrome exploit now costs less than a used truck. Security firm XBOW says its agents, running OpenAI's publicly available GPT-5.6 Sol, built a full-chain Chrome exploit in six days for about $40,000 in compute. Google paid a $250,000 bounty. The bugs are fixed. The economics are the story.

What actually happened

XBOW published the details on October 13:

• Six days, three bugs. The team rebuilt the chain from August 2 to August 7, 2026. According to XBOW's technical write-up, it links a bug in Chrome's V8 JavaScript engine, a flaw in the animated WebP decoder and a bug in the Crashpad crash reporter. Together, a malicious web page could run code outside Chrome's sandbox on Windows.
• About $40,000 in API charges. That figure covers model use during the rewarded six-day run, not the whole research program.
• Humans steered. Four XBOW researchers set strategy, picked where the agents searched and checked the output. The agents read Chrome's source, tested ideas and built proofs of concept.
• $250,000 from Google. XBOW says it is the first full-chain award under Google's 2026 Chrome reward rules. An earlier version of the chain was disqualified because Google already knew about one of the bugs.

CSO Online notes the chain could have reached roughly a billion Windows machines running Chrome. All three bugs were reported through Google's program and patched.

Why it matters for your business

A full browser chain used to take an elite team months. Now a small team with a public model and a five-figure API budget can build one in a week. XBOW did it for a bounty. Others will do it for ransom. Expect the gap between "bug found" and "bug exploited" to keep shrinking.

The defense is not exotic. It is patch discipline, and most small businesses skip it. XBOW's own advice: a Chrome fix only takes effect after you relaunch the browser. That is the front-desk PC that has had 40 tabs open since July. The POS terminal running a kiosk browser. The shared laptop in the back office.

Our order of operations. Enforce Chrome auto-update and a forced relaunch window through Google Admin or group policy. Inventory every machine and kiosk that runs a browser, including the ones nobody thinks of as computers. Keep payment and admin work on a separate, locked-down browser profile. Then test your own web apps before someone else does, because the same agents that read Chrome's source can read yours.

Sources: XBOW: Chrome full-chain exploit, XBOW Labs: Zero to Calc in Six Days, CSO Online.