Anthropic’s Claude Mythos Preview did not just find bugs. It showed how quickly AI can turn vulnerability discovery into a patch-management problem.
In a May 22 update, Anthropic said the gated research-preview model scanned more than 1,000 open-source projects and produced 23,019 candidate vulnerability findings. Its disclosure dashboard showed 1,726 confirmed valid findings as of May 22, but only 97 had been patched upstream.
For enterprise security teams, the pressure point is no longer discovery alone. It is knowing which AI-surfaced findings touch their environments, which are exploitable, and which fixes can move through testing and deployment before exposure grows.
Mythos turns bug discovery into a scale problem
Anthropic launched Project Glasswing on April 7, 2026, giving selected cloud, security, financial, and infrastructure organizations early access to Claude Mythos Preview for defensive security work.
Mythos Preview is not generally available. Anthropic describes it as a gated research preview for selected participants, with strengths in coding, agentic tasks, and cybersecurity work. That restricted-access approach now sits alongside a broader debate over frontier AI controls, after a US directive forced Anthropic to disable Fable 5 worldwide.
In its May 22 update, Anthropic said Mythos Preview had found an estimated 6,202 high- or critical-severity vulnerabilities among 23,019 total candidate findings. Of 1,752 high- or critical-rated findings reviewed by independent security firms or Anthropic, 1,587 were confirmed true positives, and 1,094 were confirmed as high or critical severity.
The disclosure dashboard showed 23,019 candidate findings, 1,726 confirmed valid findings, 1,596 disclosures to maintainers across 281 open-source projects, 97 upstream patches, and 88 published advisories. Anthropic cautioned that “patched upstream” does not mean the fix has been widely installed by downstream users.
Cloudflare, one of the participants, said Mythos Preview moved beyond flagging suspicious code. In Cloudflare’s testing, the model generated proof-of-concept code, ran it in a scratch environment, read the result, and adjusted its hypothesis when needed.
How AI bug hunting strains patch pipelines
The 97-patch figure shows how quickly AI-assisted discovery can outrun validation, maintainer coordination, patch creation, and production deployment. OpenAI’s Daybreak is applying similar pressure by using Codex Security to hunt software vulnerabilities and push more automated testing into defensive workflows.
Open-source software sits deep inside enterprise infrastructure, cloud services, security tools, developer platforms, and business applications. A confirmed upstream vulnerability may not affect every organization, but security teams still need to know whether the affected code appears in their environments and whether a patch has actually been deployed. That risk is no longer theoretical, with Google reporting an AI-built zero-day exploit.
Security teams should not treat every AI-generated finding as equally urgent. They should separate candidate findings from validated vulnerabilities, then use exposure and exploitability signals, including CISA’s Known Exploited Vulnerabilities catalog and FIRST’s Exploit Prediction Scoring System, to decide which fixes move first.
Mythos Preview points to a harder vulnerability-management cycle for enterprises: more plausible findings, heavier validation work, and more pressure on SBOMs, asset inventories, and patch verification workflows.
Also read: Researchers built an AI worm that can choose its own attack path, showing how agentic systems could change enterprise threat modeling.


