Skip to content
LUIGI MICCA

All articles

Front-end & architecture

AI is finding your framework's old bugs: patch monthly

Next.js has published 51 security advisories in 2026, against 14 last year. Why that is mostly good news, and the monthly upgrade routine a team now needs.

Published 5 min read

On Tuesday the Next.js team published a post with an unusually candid chart. Security advisories for the framework: 6 in 2024, 14 in 2025, 51 so far in 2026. Their explanation fits in one sentence: "AI has made it much easier to find them."

I think they are right, and I think the consequence is bigger than one framework. For years a team could treat framework upgrades as a project: something you schedule twice a year, when there is slack. That model is over. The software under your product now receives security fixes on a monthly rhythm, and the ability to apply one within days has become part of the architecture, like the database or the deploy pipeline.

The bugs are old. The searchlight is new

The most useful number in that post is not the 51. It is this: 70% of this year's vulnerabilities were in code at least a year old, and 43% in code three years old or more. These are not fresh mistakes shipped in a hurry. They are edge cases that sat in the codebase for years because finding them took more effort than anyone was willing to spend. Language models made the search cheap, for researchers and for attackers alike.

Next.js is simply the project that said it out loud. Nuxt shipped 4.6.4 on 2 November as a security release: eight advisories in Nuxt and three more in Nitro, the server underneath it. Node.js followed on 11 November with sixteen fixes across the 22, 24 and 26 lines, seven of them rated high. Three layers of the same stack, all patched inside ten days.

A fair caveat: an advisory count measures how hard people are looking, not how dangerous the software is. A project that publishes 51 advisories is a project with a working intake, a bug bounty and an outside audit. I would rather build on that than on one that publishes none. Vercel's claim that Next.js is "more secure today than it's ever been" is plausible. It is also the vendor grading its own homework, and their forecast that the yearly number will start to fall is exactly that, a forecast.

What a monthly train looks like

In July, Next.js moved to a formal security release programme: roughly once a month, announced in advance with the highest expected severity, so teams can plan and hosting providers can prepare mitigations. Since then I count four scheduled releases on their blog, in July, August, September and November, plus two out-of-band updates that could not wait.

The out-of-band ones are the reason to care. The 14 October update fixed two critical, unauthenticated remote code execution bugs, both traced to upstream dependencies. One was in an image library the framework uses for image optimisation. That is the dependency problem again, seen from the other side: you inherit your framework's dependencies along with its features.

The 3 November release was quieter: seven issues, one rated high, fixed in 16.4.5 and 15.5.29. Read the list, though, and a pattern shows. Four of the seven sit in the use cache and Cache Components machinery, and the worst can serve one tenant's cached data to another. I have written before that implicit caching is a loan. This is one of the ways it gets called in. The more a framework does on your behalf, the more of its code stands between a stranger's request and your customers' data.

What I would do

None of this needs a security team. It needs a routine, and someone whose name is on it.

  1. Know what you are running. Framework version, Node version, and whether each is still on a supported line. The November fixes landed only on Next.js 16.4 and 15.5. Nuxt 3 reached end-of-life on 31 July, so there was no 3.x release at all. The Node advisory says it plainly: end-of-life versions are always affected. They just do not get the fix.
  2. Put the release in the calendar. Next.js announced the November release a week ahead. Node has an announcement-only mailing list. A recurring half-day a month for "apply security patches" is cheaper than the emergency version of the same work.
  3. Make a patch upgrade boring. That means a lockfile, automated tests on the paths that earn money (sign-in, checkout, the forms that bring leads) and a preview deployment you can click through. If a patch release takes your team more than a day, the problem is not the patch.
  4. Read the release notes anyway. Security fixes change behaviour. Nuxt 4.6.4 flagged five such changes, including stricter rules about which responses a cached route may store. A one-line version bump can still alter what your pages do.
  5. Use the new tooling, and check its work. Since 16.4, next dev and next build warn when the installed version has a known vulnerability, and there is an experimental next upgrade --agent that hands the upgrade to a coding agent. I would happily let an agent do the bump. I would not let it be the one who decides the app still works.
  6. Switch off what you do not use. Every enabled feature is code you have to keep patched. If the app does not need a caching mode, an image pipeline or an edge runtime, leaving it off removes whole advisories from your list.

The business version

If you run a company rather than a codebase, there are three questions for your team or your agency. Which version of the framework and of Node is in production today, and is it still supported? When the last security release came out, how many days passed before it was live? And who decides, without a meeting, that a patch goes out this week?

The second answer is the one I would watch. A product that can absorb a patch in two days is in good shape, whatever the advisory count says. A product that cannot be upgraded without a project plan was already fragile; until this year nobody was searching hard enough to prove it.


I'm an independent software architect focused on front-end work. The dates, counts and version numbers above come from the Next.js, Nuxt and Node.js release notes linked in the text; the opinions are mine.

Written by

Luigi Micca

Software architect with a front-end focus, based in Seville.

If this is close to something on your desk: a free 30-minute intro call — no preparation needed, no obligation.

Book a call Or write to me