Samuel Arendt

Next.js hits 51 security advisories in 2026 and now warns at build time about vulnerable versions

On November 17, 2026, the Next.js team published its count of security advisories for the framework: 6 in 2024, 14 in 2025 and 51 in 2026 so far. According to Vercel, 70% of this year's vulnerabilities were in code at least one year old, and 43% in code three years old or more. The team's explanation is that AI models have made it cheaper to find old bugs, for researchers and attackers alike, and that part of the issues came from image libraries Next.js depends on.

The same post announces two practical changes. Starting with Next.js 16.4, next dev and next build warn when the installed version has a known vulnerability, and DevTools shows the alert with a ready-made prompt for a coding agent. And npx next@canary upgrade --agent checks the advisories, picks the latest safe release within the oldest major version that has a fix, and hands the upgrade to an agent along with the migration guides. The documentation marks this command as experimental.

Security fixes now arrive monthly

Since July, Next.js has shipped security fixes on dates announced in advance, roughly once a month, with the highest expected severity stated in the announcement. Urgent or actively exploited issues still ship off schedule. The November release, on November 3, shipped as 16.4.5 and 15.5.29 and fixed seven vulnerabilities, four of them in caching, which I covered here.

The November 17 post does not change that schedule. It confirms the high volume should continue while the team and researchers work through the backlog of old bugs, and Vercel only says it expects the curve to come down over time.

Who needs to change their routine

Anyone running Next.js in production, on Vercel or elsewhere. The post points to the seams between the framework and the hosting layer (proxy, CDN, runtime) as a source of bypass bugs, and two of the November fixes affected only self-hosted apps running next start. Advance notice exists partly so hosting providers can put protections in place before disclosure; self-hosted teams depend on their own upgrade.

The tightest spot is for teams still on Next.js 15. The support policy extended security fixes for that version through January 31, 2027; after that, only 16 gets fixes. Next.js 14 has been unsupported since October 2025.

Agencies and teams that ship a site and then maintain it under a support contract feel this most: one upgrade a month, per project, becomes recurring work that needs to be in the price and on the calendar.

What to do now

Follow the security page on the Next.js blog, where the advance notices are posted, and set aside a monthly upgrade window with regression testing instead of treating each advisory as an emergency. If the project is on 16.4 or later, the warning in next build gives CI a point to fail or flag.

Teams on 15 have until January 31, 2027 to move to 16 without losing fixes. A version still being supported does not settle the migration decision, which is the argument of A supported version still calls for a migration decision. Anyone on 14 or earlier is already running without fixes.

upgrade --agent may reduce the work per upgrade, but it is experimental, and its output needs the same review and tests as a manual upgrade.

What Vercel has not shown yet

Vercel gave no timeline for the number of advisories to fall. There is also no date for the memory-safe image codecs the team says it is adopting, nor for when Adapters (the contract between Next.js and the hosting provider) will cover providers well enough to remove the class of boundary bugs, as the post promises. The next major version, which would change which lines are supported, has no announced date either.

If your company is weighing something similar, reach me on LinkedIn or WhatsApp.

References

A thin, irregular crack running down a smooth white plaster wall

Photo by Javad Esmaeili on Unsplash

#Operations, #Radar, #Software Quality