AWS CVE surge traced to more researchers, not AI-written code
Start here
An analysis of 231 AWS security bulletins covering 298 CVEs from January 2024 to November 2026 found bulletins rose from 15 in 2024 to 32 in 2025 and 184 in 2026, with 41 in October 2026 alone. The author traced 109 CVEs back to their introducing commits and found only two came from code with an explicit AI marker, both carrying a Co-Authored-By: Claude trailer. Of the 79 traced 2026 CVEs, 40 sit in code written before 2025, the oldest dating to 2013. The author attributes the surge mainly to more external researchers, new AI tooling to inspect, and AWS issuing 92% of its own CVEs in 2026, and warns that the bug bill for AI-written code may only arrive in 2027.
Generated from reports · updated 9 h ago
Report timeline
Follow the reports to see the event from different sides.
- Hacker News · AIAWS CVEs 2024-2026: Is AI Finding the Bugs, or Writing Them?
An analysis of 231 AWS security bulletins covering 298 CVEs from January 2024 to November 2026 found bulletins rose from 15 in 2024 to 32 in 2025 and 184 in 2026, with October 2026 alone at 41. Tracing 109 CVEs back to their introducing commits, the author found only two came from code with an explicit AI marker, both carrying a Co-Authored-By: Claude trailer, while 40 of the 79 traced 2026 CVEs sit in code written before 2025 and the oldest dates to 2013. The author attributes the surge mainly to more external researchers, new AI tooling to inspect, and AWS issuing 92% of its own CVEs in 2026, and warns that AI-written code's bug bill may only arrive in 2027.
Heat for this event
- Current, comparable range
- 8
- Peak, comparable range
- 10November 19 19:00
- Change in 24 hours
- –
The trend compares the same participants over hours observed continuously, so its range can be narrower than the current heat count. Hover or tap the chart for hourly heat; the arrow keys move through it.