35 Cves In March 2026 How Ai Generated Code Triggered A Security Meltdown
Originally published on CoreProse KB-incidents In March 2026, security teams logged 35 new CVEs where AI-generated or AI-assisted code was a direct factor. The cause was not a novel exploit, but AI...

Source: DEV Community
Originally published on CoreProse KB-incidents In March 2026, security teams logged 35 new CVEs where AI-generated or AI-assisted code was a direct factor. The cause was not a novel exploit, but AI-written code and AI-heavy libraries shipped without updated AppSec practices. More than 40,000 vulnerabilities were tracked in NVD in 2025, already overwhelming traditional workflows [6]. AI accelerates both development and exploitation, widening the gap between change velocity and control coverage. The task: treat AI as a structural shift in how vulnerabilities are created and exploited, and redesign engineering and security practices accordingly. 1. Why 35 AI Code CVEs in One Month Is a Structural Warning The March 2026 spike reflects a broader trend: 40,000+ vulnerabilities in NVD in 2025, exceeding what traditional tools can handle [6] 16,200 AI-related incidents in 2025 across 3,000 U.S. companies, up 49% YoY [3] Finance and healthcare made up over half of those incidents [3] 📊 Structu