Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
50Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9epss 0.8%
from disclosure to weapon0 days
Published on NVDSep 1
1st PoCAug 25
exploitation probability
0.8%top 45% of all CVEs
observed exploitation
nono source reports it
4 public exploit(s)
Next.js is a React framework for building full-stack web applications. From 13.4.0 until 15.5.24 and 16.3.3, Next.js applications using Pages Router or App Router without Cache Components on Windows-hosted servers do not consistently escape backslashes in route segments before constructing incremental-cache paths. In packages/next/src/shared/lib/router/utils/escape-path-delimiters.ts and packages/next/src/server/lib/incremental-cache/file-system-cache.ts, a remote request can supply encoded Windows path separators that traverse outside the intended cache root and expose private build data, including the server-reference-manifest encryption key. Disclosure of that key can enable remote code execution in the affected application. This issue is fixed in versions 15.5.24 and 16.3.3.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
vercel · next.jspublic PoCs found — 4
githubgithub.com/rafabd1/CVE-2026-75604-poc★ 84githubgithub.com/HackSpeak/CVE-2026-75604★ 1githubgithub.com/e4zyy/Project-CVE-2026-75604★ 1githubgithub.com/FORTBRIDGE-UK/cve-2026-75604★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/vercel/next.js/commit/968b9fcb26bdeb8e0a861a9df05361474666d51bhttps://github.com/vercel/next.js/commit/b0f3460a92b955d3ca41fccff9a525a2b910fbf3https://github.com/vercel/next.js/releases/tag/v15.5.24https://github.com/vercel/next.js/releases/tag/v16.3.3https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36