Anthropic's Project Glasswing: Claude Mythos Found 10,000 Critical Zero-Days in 30 Days

The wolfSSL Story: CVE-2026-5194

Among the most significant findings was a vulnerability in wolfSSL, an open-source cryptographic library used by billions of devices worldwide — from IoT hardware to embedded systems to network equipment. Mythos identified a certificate-forgery flaw in wolfSSL and built a working exploit that could spawn fake banking sites that no major browser would warn against.

The flaw was assigned CVE-2026-5194 with a CVSS score of 9.1 — critical severity. A working exploit for this class of vulnerability does not just enable phishing sites. It enables man-in-the-middle attacks that intercept encrypted traffic at scale, undermining the core trust model that TLS/SSL provides. When Federal Reserve Chairman Jerome Powell and Treasury Secretary Scott Bessent convened a meeting with major US bank CEOs specifically to discuss the cyber risks raised by Project Glasswing, CVE-2026-5194 was reportedly among the primary examples on the table.

The wolfSSL maintainers patched CVE-2026-5194 after coordinated disclosure from Anthropic. But wolfSSL is embedded in firmware on devices that do not receive regular software updates. Patching a library in an open-source repository does not patch every device that shipped with the vulnerable version years ago — and those devices remain exposed indefinitely.

The Patching Crisis No One Anticipated

The most underreported aspect of Project Glasswing’s first month is what happened on the receiving end of all those vulnerability disclosures. Open-source maintainers — often small teams or solo developers who volunteer their time — began receiving floods of critical bug reports faster than they could process them.

Multiple maintainers reportedly asked Anthropic to slow the pace of disclosures. This is a novel situation in the history of vulnerability research. Responsible disclosure norms have always assumed that the limiting factor on patching is discovery — finding the bug. Project Glasswing flipped that assumption entirely. The AI-driven discovery rate now exceeds the human patching rate by a significant margin, and that gap will only widen as more capable models are deployed.

This creates a dangerous window. Between the moment Anthropic discovers a vulnerability and the moment a patch is deployed and adopted at scale, there is a period where the vulnerability exists in a partially-disclosed state. Security researchers and Glasswing partners know about it. Anthropic knows about it. But the vulnerability may also be present in production systems at millions of organizations that have not yet applied the patch — or whose vendor has not yet released one.

Anthropic has stated there is a six-to-twelve month window to patch the most critical flaws before adversaries build models with comparable vulnerability-discovery capabilities. That window is already running.

Claude Security: The Enterprise Complement to Glasswing

Alongside Project Glasswing, Anthropic has launched Claude Security in public beta — a separate product built on Claude Opus 4.7 (the publicly available model, not Mythos Preview). Claude Security is designed for enterprise teams who want continuous vulnerability scanning on their own codebases without waiting for Glasswing access.

According to Anthropic, Claude Security has already helped patch over 2,100 corporate vulnerabilities across its beta users. The product integrates with existing CI/CD pipelines and provides automated threat model generation, codebase mapping, and prioritized remediation guidance.

The distinction matters: Project Glasswing uses Mythos Preview (the unreleased, significantly more capable model) to scan critical global infrastructure with ~50 controlled partners. Claude Security uses Opus 4.7 and is accessible to any enterprise security team. The raw capabilities differ significantly, but Claude Security offers a practical entry point for organizations that want AI-assisted security today.

What This Means for Every Developer

The implications of Project Glasswing extend beyond the organizations directly involved in the program. Here is what matters for the broader developer community:

• Your open-source dependencies are higher risk than previously modeled. If Mythos found thousands of critical vulnerabilities in 1,000+ repositories in one month, the open-source dependencies in your production software likely contain flaws that have not yet been discovered — or that have been discovered but not yet patched at your pinned version. Running dependency audits with npm audit, pip-audit, or Trivy is now table stakes, not optional maintenance.
• Cryptographic libraries deserve special attention. The wolfSSL finding is a direct warning for any codebase that relies on open-source cryptography libraries. If your application handles TLS termination, certificate validation, or any cryptographic operation using a library maintained by a small team, it should be on your audit list immediately.
• The patch gap will widen before it narrows. As AI-powered vulnerability discovery scales, the rate of newly discovered critical flaws will outpace organizational patching capacity for most companies. Security teams need to prioritize ruthlessly — patch the highest-CVSS vulnerabilities in your most critical systems first, and automate detection of new CVEs via CI tooling.
• Your threat model needs updating. The security posture that was adequate in 2024 assumed human-speed adversaries scanning your systems. That assumption is no longer valid. Both defenders (via tools like Claude Security) and potential attackers (via models similar to Mythos, which will inevitably proliferate) now operate at AI speed. Design your security architecture with that assumption baked in.

How to Access AI Security Tooling Now

Project Glasswing itself is not broadly available — the roughly 50 partner slots are reserved for organizations operating critical infrastructure. However, several pathways exist for developers who want to leverage AI-assisted security today:

1. Claude Security public beta: Available to enterprise teams via Anthropic. Built on Opus 4.7 and designed to integrate with existing development workflows. This is the most direct path for most organizations.
2. Claude Opus 4.7 via API: For security teams with engineering resources, Opus 4.7 can be prompted to perform code review, threat modeling, and vulnerability identification. Not Mythos Preview, but a strong baseline for structured security audits.
3. VulnCheck CVE tracking: VulnCheck is tracking CVEs attributed to Anthropic researchers and Project Glasswing. Their feed provides a signal for which disclosures are coming from Glasswing research, helping security teams prioritize patches linked to AI-discovered vulnerabilities.
4. Open-source scanning integration: Tools like Trivy, Snyk, and Dependabot now incorporate CVE data that includes Glasswing-discovered vulnerabilities. Integrating these into your CI pipeline provides automated detection of newly disclosed flaws as they hit the NVD database.

The Broader Implication: AI as Proactive Security Infrastructure

Project Glasswing represents something qualitatively new: AI operating as proactive security infrastructure rather than reactive tooling. Traditional security tools — antivirus, WAFs, SIEM platforms — detect attacks after they begin or prevent known exploit patterns. Project Glasswing finds vulnerabilities before attacks exist, giving defenders a window to eliminate entire attack surfaces before adversaries know they are there.

The organizations that integrate AI security tooling into their development lifecycle now will be meaningfully more resilient than those that wait. Anthropic is moving toward a broader release of Mythos — a May 24 report from TechTimes noted the company is closer to general availability, with the Glasswing vulnerability remediation program serving partly as a prerequisite condition. When Mythos does ship broadly, every security team in the world will have access to the same capability that just found 10,000 critical bugs in 30 days.

The organizations that have built the workflows, integrations, and patching processes to handle AI-generated vulnerability reports at scale will be ready. The ones that have not will face a patching crisis of their own — simultaneously, across all their dependencies, when the six-to-twelve month window closes.

Conclusion: The Window Is Open — Use It

Project Glasswing is not a product announcement. It is a disclosure that the frontier of AI capability has crossed a meaningful threshold: one AI model, operating for one month, found more critical vulnerabilities than most human security research organizations discover in years. The Federal Reserve convened bank CEOs. Open-source maintainers are overwhelmed. And the model responsible is not yet publicly available.

For developers, the takeaway is not panic — it is urgency. Audit your critical dependencies this week. Prioritize patching high-CVSS vulnerabilities in your most exposed systems. Integrate AI-assisted security scanning into your CI/CD pipeline before Mythos (or a competitor with equivalent capabilities) becomes generally available and the entire threat landscape shifts again. The window Anthropic describes is open. Every organization that uses it is building a genuine security advantage. Every organization that ignores it is assuming the window will stay open forever.

It will not.