Key facts
| Fact | Detail |
|---|---|
| Product | Next.js (React web framework) |
| Affected versions | 13.0.0 to 15.5.27; 16.0.0 to 16.4.0 |
| Fixed in | 15.5.28 and 16.4.1, or later |
| Severity | 8.2 High (CVSS 4.0, GitHub) |
| Who can attack | Anyone over the network, no login, no user interaction; app needs a Server Action |
| Exploited | No attacks reported as of 23 October 2026 |
| CVE published | 22 October 2026 |
What an attacker can do
Next.js is a toolkit from Vercel for building websites with React. Apps built on its App Router (one of its two ways to organise an app's pages; the other is the Pages Router) can use Server Actions.
An attacker can send specially built web requests to one of these Server Actions. The Next.js server process then uses too much CPU and stops answering other requests. If the app runs as a single process, the whole site stops responding. This is a denial of service (an attack that blocks normal use).
For the business, a checkout or customer portal on the app can stop working during the attack. The CVSS score (the standard severity rating, out of 10) rates the impact on data as none, so the attacker cannot read or change anything.
Who is affected
The flaw is in next, the Next.js package on npm (the public registry of JavaScript packages). The vendor advisory lists two affected ranges:
- 13.0.0 up to and including 15.5.27
- 16.0.0 up to and including 16.4.0
Your app is exposed only if it uses the App Router and has at least one Server Action. Other Next.js apps are safe from this flaw.
Next.js also points to a related advisory in React, the library it is built on: 'Denial of Service in Server Functions' (GHSA-h3gv-c5rc-p453).
The attacker needs no account and no help from a user. Network access to the site is enough. The package is very common: npm counted 41,069,423 downloads of next from 12 to 18 October 2026.
How to check your version
Run one of these commands in the project folder. Each prints the installed version of next.
npm ls next
npx next --version
This one also prints the versions of react, react-dom, Node.js and the operating system:
npx next info
Compare the result with the ranges above. Apps on 13.x, 14.x or 15.0 to 15.4 get no patch of their own. They must move to 15.5.28 or 16.4.1.
Then check whether the app uses Server Actions. In Next.js code, a 'use server' line marks them. Search your source code for it:
grep -rl "use server" --exclude-dir=node_modules --exclude-dir=.next .
If the search lists files and the app uses the App Router, treat the app as affected.
What to do now
Update next today, then rebuild and redeploy. On Next.js 13, 14 or 15, run the first command. On 16, run the second. Any later version also fixes the flaw:
npm install next@15.5.28
npm install next@16.4.1
Vercel lists no workaround: updating is the only fix.
Version 16.4.1 also fixes a second flaw, GHSA-2464-fhr4-w9xw, which Vercel rates 9.5 Critical (CVSS 4.0). It is a remote code execution flaw (the attacker runs their own code on your server) that needs no login. It hits the Image Optimization API, the part of Next.js that resizes images, when it handles SVG files on Linux servers with glibc (the standard system library on most Linux distributions). The cause is CVE-2026-96889 in librsvg, an image library, which Red Hat rates 7.8 High (CVSS 3.1).
Next.js 16.4.1 blocks it by requiring version 0.35.5 or later of sharp, the image package that bundles librsvg. Version 15.5.28 still accepts sharp 0.34.x, which is vulnerable. On that version, check which sharp version is installed:
npm ls sharp
If it shows a version below 0.35.5, run one of these commands, then rebuild:
npm update sharp
npm install sharp@0.35.5
If you cannot update Next.js today, sharp 0.35.5 or later blocks this second flaw only. These updates fix the copy of librsvg that ships with sharp. A librsvg installed with the operating system, such as librsvg2 on Red Hat Enterprise Linux, needs the operating system's own update.
The same 16.4.1 release fixes a third Critical flaw, GHSA-673q-mjm6-r5xr.
As of 23 October 2026, Vercel's advisory does not mention any attacks, and CVE-2026-94482 is not on the Known Exploited Vulnerabilities list kept by CISA, the US cyber defence agency. Watch for a Next.js process stuck at high CPU while other requests hang.
Get help
Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.
A penetration test of your web app and its API: who can see whose data, and what an attacker can change.
From AED 20,000, excl. 5% VAT
Sources
- CVE-2026-94482 record CVE Program
- Denial of Service in App Router using Server Actions (GHSA-p3m5-59mp-jv5r) Vercel (Next.js maintainers) on GitHub
- Next.js Security Update for Upstream Vulnerabilities (14 October 2026) Vercel / Next.js
- Denial of Service in Server Functions (GHSA-h3gv-c5rc-p453) React maintainers (react/react) on GitHub
- CVE-2026-94482 detail NIST National Vulnerability Database
The same update also fixes CVE-2026-96889.