Anthropic study shows AI needs hours, not weeks, to build exploits from security patches

· Source: The Decoder · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Cybersecurity & Data Privacy, Emerging Technologies & Innovation · Depth: Intermediate, medium

Summary

An Anthropic security research study, published June 10, 2026, demonstrates that large language models (LLMs) can rapidly develop exploits from software security patches. The study tested six Claude models, including the unreleased Mythos Preview, against Firefox's SpiderMonkey engine and Windows kernel vulnerabilities. Mythos Preview crashed 14 of 18 Firefox vulnerabilities within 40 minutes, generating 8 exploits in 12 hours. The first was ready within an hour, 18 days before Firefox 148 shipped. Against 21 Windows kernel vulnerabilities, Mythos Preview identified 18 in under six hours for about \$2,200. It built 8 full privilege escalation chains for roughly \$15,700, all before typical patch deployment. This capability, also present in public and open-source models, renders traditional "N-Day" patch strategies obsolete. It replaces them with an "N-Hour" reality, increasing risk for slow-to-update systems.

Key takeaway

For Security Engineers managing patch deployment, you must recognize that traditional "N-Day" vulnerability windows are now "N-Hour." Your patch management strategies, especially for critical systems, require immediate acceleration. You should prioritize rapid deployment, consider automated patching solutions like Windows Autopatch, and advocate for memory-safe language adoption in development. Re-evaluate your organization's vulnerability risk assessments, as LLMs can exploit flaws previously deemed "unlikely."

Key insights

LLMs can build software exploits from patches in hours, not weeks, fundamentally changing cybersecurity defense timelines.

Principles

Method

LLMs analyze patch diffs, debug symbols, and public advisories to reverse-engineer vulnerabilities and generate working exploits, even without source code access.

In practice

Topics

Code references

Best for: CTO, VP of Engineering/Data, Executive, AI Security Engineer, Security Engineer, AI Scientist

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Decoder.