CVE-2026-75604 PoC and fix: Next.js remote code execution on Windows servers

CVE-2026-75604 is a critical (CVSS 9.0) path traversal in Next.js 13.4.0 to 15.5.23 and 16.0.0 to 16.3.2 that leads to remote code execution, only when the server runs on a Windows filesystem. A public proof of concept exists. There is no workaround: upgrade to 15.5.24 or 16.3.3 at least, and in November 2026 to 16.4.5 or 15.5.29. Linux and macOS servers are not affected.

The team behind Keybrum's attacksUpdated 9 min read
CVE-2026-75604critical · CVSS 9.0
Component
Next.js incremental cache on Windows-hosted servers (next)
Affected
Next.js 13.4.0 to 15.5.23 and 16.0.0 to 16.3.2, on servers with a Windows filesystem, without Cache Components
Fixed in
15.5.24, 16.3.3. Current patches: 16.4.5 or 15.5.29
Published
September 1, 2026
Does it reach a version you install? Drop your lockfile in the dependency checker: it reads every package, this one included.

In short

  • On a Next.js server that runs on a Windows filesystem, a request with no login can read private build files, among them the key that protects Server Actions. That key opens the way to running code on the server. GitHub scores it 9.0, critical.
  • Affected: next 13.4.0 to 15.5.23 and 16.0.0 to 16.3.2, without Cache Components. Linux and macOS servers are not affected, so the same app can be exposed on one host and not on another.
  • The advisory gives no workaround. The fix is 15.5.24 or 16.3.3, published on 25 August 2026. In November 2026 the current patches are 16.4.5 and 15.5.29. Next.js 13 and 14 get no fix.
  • A public proof of concept exists. CISA does not list the CVE as exploited, and we found no report of an attack.
  • If you set NEXT_SERVER_ACTIONS_ENCRYPTION_KEY yourself, upgrading does not change it. Generate a new key after you patch a Windows server that was exposed.
On this page

What CVE-2026-75604 is, in plain words

Next.js keeps rendered pages in a cache on disk, so it does not rebuild them on every visit. It calls this the incremental cache. To find a page in that cache, the server builds a file path from the route segments of the URL. Before it builds the path, it escapes the characters that separate folders, so that a segment can never point outside the cache folder.

The escape covered the forward slash. On Windows the backslash separates folders too, and Next.js did not escape it consistently. NVD's description names the two files involved, escape-path-delimiters.ts and file-system-cache.ts, and the result: a remote request can supply encoded Windows path separators that climb out of the cache folder and expose private build data. This is a path traversal: a request that makes the server read a file from a folder it was never meant to serve.

The file that matters holds the Server Actions encryption key. Next.js uses that key to protect the variables a Server Action captures, which travel to the browser and back. Its data security guide says a new private key is generated every time the application is built. NVD states the consequence in one line: disclosure of that key can enable remote code execution in the affected application. Remote code execution (RCE) means a stranger runs commands on your server, with everything your app can reach: the database, the environment variables, the files.

What a stranger can do with it

Your Next.js serverWhat a request with no login can do
Windows filesystem, next 13.4.0 to 15.5.23 or 16.0.0 to 16.3.2, no Cache ComponentsRead private build files, including the Server Actions encryption key, then run code on the server
Windows filesystem, 15.5.24, 16.3.3 or laterNothing through this flaw: the backslash is escaped, and a path that leaves the cache folder is refused
Linux or macOS, any versionNothing through this flaw: the advisory says Linux and macOS are not affected
Any operating system, a version before 15.5.24 or 16.3.3Other flaws still apply. The same release fixed a second critical one, in the image optimizer, which the release post does not limit to Windows
From GitHub advisory GHSA-p293-qw3h-jr36, NVD and the August 2026 security release post.

Severity, proof of concept and exploitation status

GitHub, the numbering authority for the Next.js maintainers, scores it 9.0, critical, with the CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H: reachable over the network, no account, no click from a victim, full impact on the server. The one brake is attack complexity, rated high: the attack depends on a condition the attacker does not control, a server on Windows. NVD has not added a score of its own.

Who is affected

Three conditions together: an affected version, a server on a Windows filesystem, and Cache Components turned off.

ConditionExposedNot exposed
Next.js version13.4.0 to 15.5.23, 16.0.0 to 16.3.215.5.24, 16.3.3 and later. Versions before 13.4.0 are outside the published range
Operating system of the serverWindows: a Windows Server machine, a Windows container, a cloud plan created with WindowsLinux and macOS
Cache ComponentsOff: no cacheComponents: true in your Next.js configApps that turned Cache Components on
RouterPages Router and App Router are both namedThe advisory excludes neither

The wording differs between sources. The advisory says applications using Pages and App router without Cache Component. The release post says both the Pages Router and App Router. NVD says Pages Router or App Router. Read it the careful way: if your server runs on Windows and you have not enabled Cache Components, treat the app as affected, whichever router it uses.

Many hosts never put you in this case. Vercel, for example, builds on Amazon Linux 2023 according to its documentation. The exposed apps are the ones where someone chose Windows: an internal tool on a Windows Server machine, Node behind IIS, a Windows container, a cloud plan created with Windows as its operating system.

A dev server on your own Windows laptop, bound to localhost, is not reachable from the internet. Upgrade the project anyway, so that no later deployment ships an affected version.

How to check your own app

Two facts decide it: the installed version, and the operating system of the machine that answers production traffic.

bash
# Installed version: use the line for your package manager
npm ls next
pnpm why next
yarn why next

# Operating system of the machine that runs the server.
# Prints win32 on Windows, linux on Linux, darwin on macOS
node -p "process.platform"
Run the second command on the production server or inside its container, not on your laptop. Anything from 13.4.0 to 15.5.23 or 16.0.0 to 16.3.2 on win32 is affected.

Then confirm what production runs: open your live site, open the browser console and type next.version. Search your Next.js config for cacheComponents to see whether the feature is on.

Keybrum has no attack for CVE-2026-75604. Proving it on a live server would mean pulling a private key out of the build folder and using it to run code, and Keybrum never runs remote code execution on an app. For this CVE, the version and the operating system are the test. What Keybrum does prove on a Next.js app is listed in the Next.js security guide: middleware bypasses, Server Action flaws, exposed source maps and .env files.

How to fix CVE-2026-75604

Upgrade. The advisory is blunt: there is no known workaround for affected Windows-hosted applications. The first fixed versions are 15.5.24 and 16.3.3, published on 25 August 2026. The fix does two things: it adds the backslash to the characters escaped in a route segment, and it makes the cache refuse any file path that ends up outside its own folder.

In November 2026 those two versions are a floor. Later releases fixed more, including the image optimizer flaw GHSA-2464-fhr4-w9xw in October. The security release of 3 November 2026 ships 16.4.5 for the 16.x line and 15.5.29 for 15.x. No 13.x or 14.x release fixes this CVE: those apps need a major upgrade.

bash
npm install [email protected]
# or, to stay on 15
npm install [email protected]
Commit the lockfile, rebuild and redeploy. A new build also creates a new Server Actions key, unless you pinned one.

If you cannot upgrade today

No setting closes the hole, so reduce who can reach the server until you patch. Put the app behind a VPN or an IP allow list if it is an internal tool. Move it to a Linux host or a Linux container if that is faster than the upgrade: the flaw needs a Windows filesystem. A firewall rule that drops requests with an encoded backslash in the path may stop the public proof of concept, but the advisory does not offer it as a workaround, so do not count it as a fix.

What to do after upgrading

  1. 1

    Confirm production runs the fixed version

    Type next.version in the browser console on the live site, and make sure no old process or container still answers on the Windows server.

  2. 2

    Replace a pinned Server Actions key

    Next.js generates a new key on each build, so a rebuild on the fixed version replaces a key that leaked. The exception is a key you set yourself in NEXT_SERVER_ACTIONS_ENCRYPTION_KEY to keep several servers in sync: it survives every build. Generate a new one, for example with openssl rand -base64 32 as the Next.js docs suggest, set it on every server and rebuild.

  3. 3

    Treat the server's secrets as read if it was exposed

    NVD describes the leak as private build data, and a successful attack ends with code running on the server, where every environment variable is readable. If an affected version faced the internet on Windows, rotate the database password and the API keys the app uses. Our guide on what to do with a leaked key gives the order to follow.

  4. 4

    Read the access logs

    Search the weeks before your patch for requests whose path carries an encoded backslash. A hit does not prove a break-in. It tells you someone tried.

Then look at the rest of the app. A framework patch closes the framework's hole. It does not check who may read which record. The vibe coding security risks guide covers that side.

AdvisoryWhat it doesFixed in
GHSA-2xp9-vwfh-vxw4Remote code execution when the image optimizer processes an attacker-controlled AVIF image. Same release as this CVE15.5.24, 16.3.3, which disable AVIF optimization
CVE-2026-44578Server-side request forgery through WebSocket upgrades on self-hosted servers15.5.16, 16.2.5
CVE-2025-55182 (React2Shell)Remote code execution in React Server Components, exploited in the wild16.0.7 and the matching 15.x patches
GHSA-2464-fhr4-w9xwRemote code execution through an SVG the image optimizer processes, on glibc Linux15.5.28, 16.4.1

Timeline

DateEvent
17 August 2026CVE ID reserved by GitHub
25 August 2026Next.js 16.3.3 and 15.5.24 published. The security release, announced a week earlier, is moved forward that day for a second critical flaw in an upstream dependency
1 September 2026CVE record and NVD entry published
3 September 2026CISA's assessment: exploitation none, not automatable, total technical impact
8 September 2026Advisory added to the GitHub Advisory Database. SecureLayer7 publishes its analysis and points to a public proof of concept
3 November 2026November 2026 security release: 16.4.5 and 15.5.29 become the current patches
13 November 2026Still absent from CISA's Known Exploited Vulnerabilities catalog

Questions

Is there a public PoC for CVE-2026-75604?

Yes. SecureLayer7's analysis of 8 September 2026 points to a public proof of concept on GitHub. CISA has not listed the CVE as exploited, and we found no report of an attack. This page does not reproduce the exploit: check your version and your server's operating system instead.

Are apps on Vercel affected by CVE-2026-75604?

The flaw needs a server on a Windows filesystem, and the advisory says Linux and macOS are not affected. Vercel's documentation gives Amazon Linux 2023 as the base of its build image. Upgrade anyway: the same release fixed a second critical flaw in the image optimizer.

Is Next.js on Linux or in Docker affected?

Not on Linux, per the advisory. A container is affected only if it runs Windows. Run node -p "process.platform" inside it: linux means this CVE does not apply, win32 means it does.

Is there a workaround for CVE-2026-75604?

No. The advisory says there is no known workaround for affected Windows-hosted applications. Upgrade to 15.5.24 or 16.3.3 at least, 16.4.5 or 15.5.29 in November 2026, or move the app to a Linux host until you can.

Is Next.js 14 affected?

Yes, when the server runs on Windows: the range starts at 13.4.0, and no 13.x or 14.x release fixes it. The fix exists only in 15.5.24, 16.3.3 and later, so a 14.x app needs a major upgrade.

Do I need to rotate keys after patching?

A rebuild creates a new Server Actions key by default. If you pinned one in NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, generate a new value. If an affected version faced the internet on Windows, also rotate the database password and the API keys the server holds.

Sources

  1. 1.GHSA-p293-qw3h-jr36: Unauthenticated Remote Code Execution on windows-hosted servers, Vercel (Next.js) on GitHub
  2. 2.CVE-2026-75604, NIST National Vulnerability Database
  3. 3.CVE-2026-75604, CVE Program
  4. 4.GitHub advisory database: GHSA-p293-qw3h-jr36, GitHub
  5. 5.August 2026 Security Release, Next.js Blog
  6. 6.Fix ISR misses with backslashes in segments when deployed on Windows (fix commit, 16.3.x), Vercel (Next.js) on GitHub
  7. 7.Next.js v16.3.3 release notes, Vercel (Next.js) on GitHub
  8. 8.Data security: closures and encryption, overwriting encryption keys, Next.js Docs
  9. 9.cacheComponents, Next.js Docs
  10. 10.November 2026 Security Release, Next.js Blog
  11. 11.Known Exploited Vulnerabilities Catalog, CISA
  12. 12.EPSS score for CVE-2026-75604, FIRST
  13. 13.CVE-2026-75604: Next.js Windows cache path traversal, SecureLayer7
  14. 14.Build image overview, Vercel Docs

Your app is public. So are its mistakes.

Check what any attacker can already see in it, free, in ten seconds. The full attack, with proof and fixes: €49 once, or €29 a month on a plan.

or continue with Google or GitHub