If you run a website or application on Next.js, the latest number from the framework's own team deserves a pause: 51 security advisories in 2026, against 14 in 2025 and 6 in 2024. In a post published on 17 November 2026, the Next.js team explains why the count is rising and ships tooling to keep projects on a patched version. For a business, the real question is not whether the framework has bugs, but which version your app is running right now.
Why Next.js advisories are rising so fast
According to the Next.js team, the main driver is AI making bugs cheaper to find. Edge-case flaws that were once too impractical to exploit are now worth fixing. Of this year's 51 vulnerabilities, 70% sat in code at least a year old, and 43% in code three years or older.
Part of the problem also comes from dependencies, especially the image libraries behind image optimization. That code path often touches user-supplied input, so the risk is higher. The team says it is moving towards memory-safe image decoders.
On the process side, Next.js combines a bug bounty, an internal triage bot, a manual audit by Trail of Bits, and a security agent that reviews every pull request. Security releases now ship roughly once a month and are announced in advance, so you can plan upgrades.
The November patch: cache bugs that can leak data between users
The security release of 3 November 2026 shows the kind of risk to watch. Fixes landed in Next.js 16.4.5 (Active LTS) and 15.5.29 (Maintenance LTS). Most issues involve Cache Components and use cache:
- High severity: when the same public
use cachefunction is called both directly and throughunstable_cache, content can be returned across root parameter values. If the root parameter is a tenant ID, the result may contain another tenant's data. - Medium severity: nested
use cachefunctions can serve content generated for one locale or site to requests for another. - Medium severity: different binary arguments can produce the same cache key, so one user's cached result may be served to another.
- Medium severity: self-hosted apps running
next startwith Cache Components can have a shared page shell poisoned by an unauthenticated request.
What they share is cross-user data exposure, an incident businesses struggle to accept, particularly in multi-tenant systems.
Vulnerable-version warnings right in your terminal
Starting with Next.js 16.4, both next dev and next build tell you when the version you are running has a known vulnerability. During development, DevTools also shows a Vulnerability Insight with a prompt you can paste into your coding agent.
To automate the upgrade, the team suggests:
npx next@canary upgrade --agentThe command checks your version against the advisories and picks the latest safe release within the oldest major line that has a fix, so you are not forced into a major upgrade just to get a patch. It then hands the work to your coding agent with the matching migration guides. Treat it as an aid, not a substitute for review and testing.
What your engineering team should check this week
- Confirm the version that is really running. Look at
package.jsonand the lockfile, and more importantly at the version inside the Docker image running in production; the two often drift apart.
npm ls next- Compare against the patched releases. The 16.x line needs at least 16.4.5 and the 15.x line at least 15.5.29 for the November fixes. Also check the latest advisory list on the Next.js security page, since newer releases may exist.
- Find out whether you use Cache Components. Search the source:
grep -rn "use cache\|unstable_cache" app src --include=*.ts --include=*.tsxIf a cached function reads a tenant, locale or user identifier, verify that the cache key really includes those values, and avoid passing binary arguments that carry authorization meaning.
- Put the check into CI. Run
next buildin your pipeline and treat the vulnerability warning as a signal to act on, rather than something only seen on a developer laptop. - Schedule it. Since patches arrive about monthly and are announced ahead of time, reserve a fixed window for upgrading and testing instead of emergency patching late at night.
If your projects run on Node.js, do not forget the runtime: see Node.js patches 16 vulnerabilities: HTTP/2 and TLS need updating now. For the database layer, there is PostgreSQL 18.7 and 52 vulnerabilities.
A note if you outsource software development
If a third party builds and runs your application, ask directly: which Next.js version is live, who owns the monthly security upgrade, and is there regression testing after each patch? Writing this into the maintenance agreement is far cheaper than handling a customer data leak. You can see how we deliver software on our projects page, or talk to us about reviewing and upgrading the Next.js applications you already run.
References
- How we're using AI to make Next.js more secure, Next.js, 17 Nov 2026
- November 2026 Security Release, Next.js, 3 Nov 2026






