· ai-devtools
How we're using AI to make Next.js more secure
In this post, we want to explain why you’re seeing more advisories, how we’re using AI to prevent security bugs in new code, and how we’re making it easier for all apps to make sure they’re always running a secure version of Next.js. > npm run dev ⚠️ Installed Next.js version 16.4.0 is affected by a known security vulnerability.
The simple answer is that AI has made it much easier to find them. Any popular open-source project with a working process for receiving security reports should expect to see an increase in advisories in the current era, as LLMs with ever-increasing capabilities are becoming more widely available. But why the increasing number over time?
Part of the answer is that every framework has a backlog of edge-case bugs that were never discovered or were too impractical to exploit. With AI, finding and exploiting them has become cheap, turning these bugs from edge cases into risks that are now worth fixing. Of the 51 vulnerabilities discovered this year, 70% of them were in code at least one year old, with 43% coming from code three years or older. And we’re seeing this same pattern in other mature frameworks and programming languages across the industry.




