A site with no feed of its own. Its index page is checked for new posts, which are read the same way. What Trove read and did not keep stays on file, not shown.
XBOW describes building a Chrome full-chain exploit, made of three independent bugs, that takes a user from an ordinary web page to remote takeover of a Windows machine. The team built it in six days with a publicly available model (GPT-5.6 Sol) for about $40,000 of compute, and Google paid a $250,000 bounty, the first under its 2026 rules. The bugs are now fixed. The post covers the human-agent workflow, the modular design that allowed swapping in a backup bug after Google said it already knew one, and the claim that agents could find each bug on their own within a year.
ChromeWindowsXBOW+1
GPT-5.6 SolBrendan Dolan-GavittBlack Hat+2
Offensive Security, AI Security· 2026-10-13T15:20:00+00:00
XBOW's technical write-up on CVE-2026-72018, an out-of-bounds write in the Linux kernel's SMC-D/DIBS loopback code (dibs_loopback driver) that lets an unprivileged user with CAP_NET_ADMIN escalate to root. The bug stems from an unvalidated peer-controlled dmbe_idx/dmbe_size offset computation (smcd_conn_save_peer_info -> smc_ism_write -> dibs_lo_move_data memcpy) that XBOW turned into a reliable LPE by MITM-forging CLC handshake fields via nftables NFQUEUE and grooming kernel cred structures with a 16-byte zero-write primitive alone. The post also details where the autonomous agent's reasoning stalled (abandoning a promising MITM idea, confusing write-what-where with a pure zero-write, chasing an unnecessary UAF) and required human intervention, motivating a multi-agent redesign of XBOW's research pipeline.
Linux kernelXBOW
CVE-2026-72018
Offensive Security, AI Security· 2026-09-28T18:02:55.976+00:00
XBOW benchmarked an early Grok 4.7 build against Grok 4.6 on its production exploit-crafting harness and a broader agentic pentesting evaluation across large targets. Raw results were mixed or slightly regressive, but splitting by orchestration showed Grok 4.7 performs substantially better inside xAI's Build agent environment (68 vs 42 true-positive findings) due to a shift toward shorter, atomic tool-call steps, while a reasoning-effort "stuck-in-planning" failure mode seen in 4.6 (~0.85% of runs) disappeared entirely in 4.7.
GrokXBOWxAI Build+1
Grok 4.6Grok 4.7GPT-6+2
AI Security, Offensive Security· 2026-09-21T18:00:00+00:00
xbow.comarticle
