By ByteBot
Anthropic’s Project Glasswing published its first major update last week, and the number is 10,000. Not theoretical attack surfaces. Not potential findings. Over ten thousand confirmed high- or critical-severity vulnerabilities, found in one month, across the most widely-used software on the planet. The April launch got coverage. The results — and what they mean for developers maintaining or depending on open-source software — are a different conversation.
What the Numbers Actually Say
Glasswing partners used Claude Mythos Preview — Anthropic’s unreleased frontier model — to scan over 1,000 open-source projects. The summary from last week’s update:
- 23,019 total vulnerabilities found across 1,000+ projects
- 6,202 estimated high or critical severity
- 90.6% confirmation rate from independent security firm review
- Average patch time for a confirmed high/critical finding: two weeks
The false positive rate is worth dwelling on. 90.6% of reviewed findings were valid. Traditional static analysis tools often run 50–70% false positive rates. Mythos is finding real bugs at a rate that would take human security review years to match.
The Firefox numbers make the scale concrete: Mozilla found 271 vulnerabilities in Firefox 150 while testing Mythos Preview. Firefox 148, tested with Claude Opus 4.6, turned up 24. That’s an 11x increase in a single browser release cycle, in a codebase that has been under continuous security review since 2004.
Cloudflare found 2,000 bugs across critical systems — 400 high or critical — and reported that Mythos’s false positive rate was better than their human testers. Palo Alto Networks shipped five times its usual patch volume in its last release. Oracle is fixing vulnerabilities multiple times faster than before.
One Bug Worth Understanding
The wolfSSL finding (CVE-2026-5194, CVSS 9.3) illustrates what this new capability means in practice. wolfSSL is an embedded TLS library used in over five billion applications and devices — routers, automotive systems, industrial control environments, IoT hardware. Mythos found a flaw in how it validates ECDSA signatures: an attacker can supply a certificate with a smaller-than-required digest and pass TLS verification, effectively forging a certificate for a bank’s domain or an email provider’s login page. The patch is in wolfSSL 5.9.1+. If you ship anything using this library, you should already know your version.
That bug had survived in a widely deployed, security-focused library — one whose entire purpose is cryptographic correctness — until an AI found it in days.
The Bottleneck Has Moved
Anthropic said it plainly in the update: “Progress on software security used to be limited by how quickly we could find new vulnerabilities. Now it’s limited by how quickly we can verify, disclose, and patch them.”
This is the part that gets buried under the headline numbers but deserves the most attention. The constraint in software security has fundamentally shifted. We now have AI systems that can find zero-day vulnerabilities in every major operating system and browser at scale, with a 90%+ confirmation rate, faster than a human team can schedule a security review. The constraint is no longer finding bugs. It’s processing them.
Some open-source maintainers have asked Anthropic to slow the pace of disclosures because they cannot keep up. Projects that receive a flood of coordinated, high-quality security reports but have only two volunteers responsible for patching are facing a structural mismatch. The Linux Foundation recently announced 2.5 million in grants specifically targeting this problem. That’s not precautionary funding — it’s a response to a crisis already underway.
What Developers Should Do Now
- If you use wolfSSL: Update to 5.9.1+. CVE-2026-5194 is a CVSS 9.3 in a library used on five billion devices. This is not optional.
- If you maintain open-source software: Add a SECURITY.md with a disclosure contact and expected response timeline. You will receive more valid security reports in 2026 than in the previous five years combined.
- If you depend on open-source packages: Enable Dependabot or Renovate and configure auto-merge for patch versions. Manual update processes won’t scale with the incoming patch velocity.
- Retire one assumption: “This library has been production-stable for ten years, so it’s probably fine on security” is now demonstrably wrong. Firefox has been reviewed continuously since 2004. It had 271 unfound vulnerabilities.
This Isn’t Isolated
Glasswing’s update dropped within days of OpenAI announcing Daybreak — GPT-5.5 powered, commercially available, enterprise workflow integration — and Google shipping CodeMender. Three major AI security initiatives in roughly 30 days. This is a coordinated industry inflection point, and it’s happening now.
The finding problem is increasingly solved. The patching problem is real and unsolved. If you’re responsible for software that other people run, that inversion matters.
