A frontier AI model can now scan an entire open source codebase and surface exploitable vulnerabilities in minutes. That capability, once requiring expert-level skill and weeks of effort, is now broadly available — and attackers are already using it. The uncomfortable reality: of the thousands of validated open source vulnerabilities that AI has recently surfaced, fewer than 5% have been patched. On June 25, the Linux Foundation launched Project Akrites to address that gap directly.
Akrites establishes a shared Security Incident Response Team (SIRT) for critical open source software, backed by 19 founding organizations including AWS, Google, Microsoft, OpenAI, Anthropic, NVIDIA, JPMorganChase, and the Rust Foundation. The initiative is seed funded by Alpha-Omega, a Linux Foundation directed fund, and aims to be the single coordinated response channel the open source ecosystem has never had.
The Attack Surface AI Just Opened #
The threat model here has shifted fundamentally. Linux Foundation CEO Jim Zemlin put it plainly: “The mean time to exploit a vulnerability in software is now negative seven days.” Attackers are exploiting flaws before defenders have even finished discovering them. Frontier AI models accelerate the offensive side of that equation — a threat actor who previously needed deep expertise can now point a model at any open source project and get a prioritized list of attack vectors.
This isn’t theoretical. Supply chain attacks jumped 451% year-over-year according to JFrog’s 2026 annual report. The TrapDoor campaign in May hit 384 malicious packages across npm, PyPI, and Crates.io simultaneously — and even weaponized AI coding assistant config files to hijack developer tools. The JPMorganChase CISO framed it clearly: “AI has massively compressed the time between vulnerability discovery and exploitation to near real time.”
Related:[Devin Security Swarm: AI Catches 72% of Bugs at $90]
What Akrites Actually Does #
The core problem Akrites solves isn’t just slow patching — it’s fragmented disclosure. Right now, a single maintainer might receive overlapping, conflicting vulnerability reports from dozens of companies, government agencies, and independent researchers. The noise creates fatigue and delays the actual fix. Akrites’ answer is one coordinated entry point: maintainers work with a single SIRT rather than a hundred separate reporters.
The technical framework uses established industry standards — CVE identifiers, Traffic Light Protocol (TLP) markings, CVSS scoring, EPSS exploit prediction, and VEX statements. Fixes flow upstream to the original project before public disclosure, which matters: the goal is to land the patch before attackers know the vulnerability exists. For unmaintained packages with no active maintainer — and there are many — Akrites acts as maintainer of last resort.
The Sonatype CTO captured the upstream leverage: “A single vulnerable component can sit underneath thousands of organizations, which means one upstream fix can reduce risk across an entire ecosystem.” That’s the bet — coordinate the fix once, protect everyone downstream.
Why Akrites Is Different From What Came Before #
The open source security space isn’t short on initiatives. OpenSSF focuses on standards and tooling. Alpha-Omega funds security improvements in critical projects. Project Lightwell (IBM/Red Hat) backports patches into production environments. Akrites is explicitly not trying to replace any of these — it’s adding operational pre-disclosure coordination, the piece the ecosystem has been missing.
The Linux Foundation’s Mike Dolan acknowledged the challenge directly: “The space is crowded, and the track record is mixed.” That’s a fair read. Previous coordination efforts have struggled to move at the speed attacks do. Akrites’ differentiator is the single-SIRT model — instead of competing disclosure processes, one trusted team coordinates across the 19 founding organizations and beyond. SecurityWeek’s coverage notes that Akrites explicitly commits to one streamlined entry point rather than multiple vendor platforms.
Moreover, the composition of founding members signals what’s really at stake. It’s not just tech giants: financial institutions (JPMorganChase, Citi), telcos (Ericsson, Vodafone), and security vendors (Chainguard, Zscaler, Sonatype) all signed on. The sectors represented — finance, healthcare, energy, telecoms, government — are exactly the critical infrastructure most exposed when an unmaintained open source component contains an unpatched vulnerability.
What Developers Should Do Now #
Akrites doesn’t require developer action to benefit from it — the protections flow upstream. However, the 5% patch rate stat is a signal that dependency hygiene matters more than ever. If a vulnerability in a critical package goes unpatched 95% of the time, the fastest path to safety is keeping your own dependency graph current and pruning unmaintained packages before they become a liability.
The XZ Utils incident in 2024 made the structural problem visible: a single burned-out maintainer carrying infrastructure-level responsibility, without institutional support, is an exploitable attack surface. CISA’s post-mortem on XZ Utils highlighted exactly this gap. Akrites’ maintainer-of-last-resort function is a direct response. Whether a coordinated industry initiative can move faster than AI-enabled attackers is still an open question — but the alternative is the status quo, where 95% of the vulnerabilities AI finds go unanswered.
Key Takeaways #
- AI has lowered the skill barrier for vulnerability discovery — attackers can now scan open source projects in minutes, and fewer than 5% of AI-surfaced vulnerabilities have been patched
- Akrites (launched June 25) establishes a shared SIRT and single CVD process for critical open source software, replacing fragmented multi-reporter disclosure
- The “maintainer of last resort” function directly addresses abandoned critical packages — the class of problem XZ Utils exposed in 2024
- Nineteen founding organizations across AI, cloud, finance, telco, and security indicate that critical infrastructure sectors are treating this as a structural risk
- Developers benefit passively, but dependency hygiene remains the most actionable defense: keep packages updated and audit unmaintained dependencies now