AI now finds software vulnerabilities faster than they get patched
Recent developments in AI have led to a significant shift in software security dynamics. AI can now identify vulnerabilities faster than they can be patched, creating a dangerous gap in the security model. This change highlights the need for new operational strategies to manage the increasing speed of vulnerability discovery.
- ▪AI agents have found over 10,000 high- or critical-severity vulnerabilities in important software.
- ▪Only 75 out of 530 high-severity bugs disclosed by Anthropic have been patched.
- ▪The traditional software security model is now overwhelmed by the speed of AI-driven discovery.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,602 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Thenewguard |
| Canonical URL | https://thenewguard.ai/features/faster-than-we-can-patch/ |
| Publication time | Mon, 25 May 2026 10:58:29 +0000 |
| Retrieval time | 2026-05-25T11:12:36.628Z |
| Last seen | 2026-05-25T11:12:36.628Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 8T2ghVDESiN_ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
For thirty years, software security has been gated by a single scarce resource: skilled humans who can find vulnerabilities. Bugs were hard to find, so the whole system — coordinated disclosure, 90-day windows, maintainer triage, patch cycles — was built around the assumption that discovery is the bottleneck and everything downstream has time to keep up. That assumption broke this week. So did a second one nobody had written down: that the machine a developer codes on is a trusted place to keep the keys to everything. The week’s headlines were about Google’s agent stack and a $1.25-billion-a-month compute bill. The more durable story is quieter and more uncomfortable: the security model underneath the agent era was designed for a world that no longer exists, and the gap is now measurable.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Thenewguard.
Discussion
0 commentsMore from Thenewguard
