Urgent.News

What's breaking now, across thousands of outlets.

AI

Artificial intelligence created an attack for Chrome in six days

Researchers at security firm XBOW used an AI model to build a full-chain Google Chrome exploit combining three unknown bugs in six days. The agentic workflow handled source code analysis, proof-of-concept testing, and initial drafts. Google confirmed the vulnerabilities, released patches, and paid a $250,000 reward. Security firm XBOW announced that its researchers used a publicly available…

Researchers at security firm XBOW utilized an artificial intelligence (AI) model to develop a comprehensive Google Chrome exploit within six days, by combining three previously unknown vulnerabilities. The AI model managed tasks such as source code analysis, proof-of-concept testing, and the initial creation of the exploit. Upon discovery, Google acknowledged the vulnerabilities and promptly released patches, while XBOW awarded itself the maximum $250,000 reward for successfully exploiting the entire attack chain.

The attack, completed between August 2 and 7, 2026, requires no user interaction beyond visiting a compromised webpage, thus facilitating code execution on Windows systems without any prior clicks or downloads. Crucially, Google confirmed that the exploit had not been previously deployed on actual users prior to its resolution.

The AI-assisted methodology involved a six-day period of preparation and testing, costing approximately $40,000. XBOW's researchers directed the AI in searching the browser code, evaluating ideas, crafting prototypes, and drafting the exploit's initial segments. The AI focused on three distinct Chrome components: an execution engine, image reading system, and error handling mechanism.

The vulnerabilities impacted a billion Windows users before Google patched versions 152.0.7977.65 (on August 25), 152.0.7977.82 (on September 3), and the broader 152 update series.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

I finally cut AI context bloat by 80% and the fix was embarrassingly simple

A few months ago I watched an agent do something deeply cursed. It had already fetched the data. It had already parsed the data. It had already stored the useful fields.

  • AI agents previously included entire raw tool responses in subsequent model calls
  • Solution was to store full results in structured state outside the model
  • This change improved agent quality and efficiency significantly

How Do You Threat-Model an Application That Uses Autonomous AI Agents?

You spent years building a threat model you trust. You know your trust boundaries, you've mapped your data flows, and your team can recite STRIDE in their sleep.

  • Autonomous AI agents act on untrusted input, unlike traditional software.
  • Prompt injection is the new SQL injection risk for AI agents.
  • Threat modeling must include agent, tools, and memory as assets with trust boundaries.

More from Wednesday 14 October →