On November 3, 2026, the Next.js team published a security release: according to the Vercel / Next.js Blog, there are updates in versions 16.4.5 (Active LTS) and 15.5.29 (Maintenance LTS) that fix several security issues, and all operators are asked to patch their Next.js dependencies. The team had already announced the date on October 27, back then still with seven vulnerabilities rated Medium. If your website or web app runs on Next.js 15 or 16, an update is due, and not just at your next maintenance window.
Next.js is the framework that many modern websites, shops and customer portals run on. A "security release" means: the vendor has found and fixed vulnerabilities. Until you update, they stay open in your installation.
There are seven vulnerabilities, fixed on November 3, 2026 in 16.4.5 and 15.5.29. According to the blog of Samuel Arendt, one of them is rated High and six are rated Medium. That is a secondary source. The Next.js team's announcement from October 27 still spoke of seven Medium vulnerabilities, so the rating apparently changed between the announcement and the release.
What the individual vulnerabilities do in technical detail is not clear from the sources we have. The title of the Arendt post refers to cache vulnerabilities. A flaw like that can become relevant when an application serves data to different users or tenants and a cache assigns it incorrectly. That is a plausible interpretation, but not a statement from the sources about the specific vulnerability. For that, read the official release announcement and the related advisories.
For context: a cache is a temporary store. It makes sure pages and data are delivered quickly without being recalculated every time. If it makes mistakes, in the worst case the wrong content goes to the wrong visitors. On a pure information website that is annoying. On a customer portal with a login, it is a data protection issue.
Projects running Next.js 15 and 16 are affected. According to a post on DEV Community, four of the seven vulnerabilities concern the so-called Cache Components and therefore only Next.js 16, while the other three also affect Next.js 15. This is also a secondary source.
Important in practice: according to the same post, since Next.js 16.4 Cache Components are enabled by default in every new project created with create-next-app. So new projects are more likely to be affected than older ones. Whether an existing project uses the feature is something you need to check in the code, or have checked.
Hosting plays a role too. In its changelog (secondary source), Netlify writes that some of the vulnerabilities affect Next.js sites hosted on Netlify. Netlify explicitly recommends updating to 16.4.5 (or 15.5.29 for 15.x) and redeploying. The same applies, in essence, to any hosting: the update in the code isn't enough, the new version also has to go live.
On the versions:
The last point is the uncomfortable message: if you stay on 15, you have an expiry date. After that there are no more security fixes, and the next security release will hit you unpatched.
For you as an operator, it means: check which of your systems run on Next.js, and plan the update. How urgent it is depends on what the application does. A static company site without a login is less sensitive than a portal where customers or tenants see their own data.
AI projects in particular deserve a look. Many AI applications today have a Next.js frontend: the chatbot on the website, the customer portal, the dashboard for an AI agent. Behind it there are often interfaces to language models such as the Claude API or OpenAI, plus a database such as Supabase. The AI itself is not affected by the release, but the frontend is the door to the outside. And if data is served per user there, a cache error is exactly the kind of problem you don't want.
My take: A security patch is not a project but routine, and anyone who treats it like a project patches too late. Most businesses don't have a problem with the update itself. They have a problem because nobody is responsible. The agency handed the project over two years ago, the developer is gone, and nobody knows which version is running. That is the real risk.
There is an honest limit, too: a minor update within the same major version is usually straightforward, but not risk-free. If you haven't touched your dependencies for years, other packages can cause problems with the new version. That can't be judged across the board from a distance, and the sources say nothing about it. That's why a test before going live is part of the process.
Tackle it in this order: inventory, update on a test environment, tests, go live. For a manageable project, this is usually a matter of a few work steps, and you don't have to be a programmer to do it.
If you are already facing the decision of whether to move to version 16, use the January 31, 2027 deadline as a planning basis. Patching to 15.5.29 now buys you time, but you should schedule the upgrade to 16 rather than postpone it. Update maintenance can also be put into a fixed maintenance rhythm; for web projects we are happy to look at that with you under web development. You can get a rough first assessment of how your system looks from the outside with the website check.
Softstorm works vendor-independently and uses the right technology for each project, including Next.js, as on the platform Besser-Cruisen, which is built with Next.js and Payload CMS. If you are not sure whether your systems are affected or who maintains them: book a free initial consultation. Together we'll look at which version is running on your side and what to do next.
We analyze your processes, identify automation potential and show you which digital systems really make sense.