Georgia Tech SSLab · Security research · Data through Sep 26, 2026
310 published CVEs and GitHub advisories traced to AI-assisted code changes, each with the vulnerable code and the fix.
Browse all 310 findings →Star on GitHub ↗How we verify
Most common AI tool among findings that name one.
310 findings by advisory publication month, May 2025 – Oct 2026. Data through Sep 26, 2026.
| Month | Findings | Advisories researched |
|---|---|---|
| May 2025 | 2 | 6% of 890 |
| Jun 2025 | 2 | 9% of 829 |
| Jul 2025 | 0 | 6% of 824 |
| Aug 2025 | 1 | 10% of 680 |
| Sep 2025 | 0 | 4% of 1,424 |
| Oct 2025 | 0 | 5% of 1,394 |
| Nov 2025 | 2 | 9% of 492 |
| Dec 2025 | 2 | 5% of 1,690 |
| Jan 2026 | 0 | 11% of 1,131 |
| Feb 2026 | 25 | 14% of 1,356 |
| Mar 2026 | 33 | 16% of 2,437 |
| Apr 2026 | 41 | 16% of 2,558 |
| May 2026 | 44 | 14% of 3,363 |
| Jun 2026 | 40 | 18% of 2,968 |
| Jul 2026 | 55 | 16% of 3,326 |
| Aug 2026 | 35 | 14% of 3,871 |
| Sep 2026* | 2 | 6% of 634 |
| Oct 2026 | 26 | – |
Note: Only 4%–18% of each month's advisories have been researched so far, so a short bar can mean little research rather than few AI-caused vulnerabilities.
* Sep 2026 is partial, so its bar is lighter.
Who, where, and why: the AI tools involved, what went wrong, and where the vulnerable code lives.
300 of 310 findings name the tool on every AI-assisted change. Gray bars show each tool's share of the 45,156 AI-marked commits in the same repositories and window.
Claude self-marks nearly every commit; GPT/Codex and Cursor usually leave no marker, so their commit shares are floors. A findings share above the commit share is an upper bound, not proof a tool writes worse code. Shares that match mean findings track usage.
One root-cause category per finding.
Where the vulnerable code lives, including findings whose language is not yet recorded.
Repositories with the most findings. Filter the full index by repository in Findings.
See the vulnerable code and fix: one recent example of each kind of AI contribution.