CVE-2026-75604: Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

Published Sep 1, 2026
·
Updated

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.

Affected Software

4 affected components
Next.js Next.js>=13.4.0<15.5.24
Next.js Next.js=15.5.24
Next.js Next.js>=16.0.0<16.3.3
Next.js Next.js=16.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 15.5.24
  2. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 16.3.3

Event History

Sep 1, 2026
CVE Published
via MITRE·09:23 PM
Data Sourced
via MITRE·09:23 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

The issue affects Next.js applications hosted on Windows that use either the Pages Router or the App Router without Cache Components. Versions from 13.4.0 through 15.5.23 are affected, as are 16.x versions before 16.3.3.

2

What does an attacker need to exploit this?

An attacker can send a remote request containing encoded Windows path separators in route segments. No authentication or user interaction is required, although the attack complexity is rated high.

3

Why can a cache-path traversal lead to code execution?

Traversal outside the intended incremental-cache root can disclose private build data, including the server-reference-manifest encryption key. Disclosure of that key can enable remote code execution in the affected application.

4

What versions remediate the issue?

Update to Next.js 15.5.24 or 16.3.3. These versions contain the fix for the inconsistent escaping of backslashes in route segments.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203