CVE-2026-75604

Received Received - Intake

Path Traversal in Next.js Framework

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-01

Last Modified

2026-09-01

Generated

2026-09-02

AI Q&A

2026-09-02

EPSS Evaluated

N/A

NVD

CVE-2026-75604

Affected Vendors & Products

Vendor	Product	Version / Range
vercel	next.js	From 13.4.0 (inc) to 15.5.24 (inc)
vercel	next.js	15.5.24
vercel	next.js	16.3.3

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

This vulnerability affects Next.js applications running on Windows servers without Cache Components. It allows remote attackers to use encoded path separators to escape the intended cache directory and access private build data, including encryption keys. The issue exists in versions from 13.4.0 to 15.5.24 and 16.3.3.

Detection Guidance

This vulnerability affects Next.js applications running on Windows servers without Cache Components, specifically versions between 13.4.0 and 15.5.24 or 16.3.3. To detect it, check your Next.js version using 'npm list next' or 'yarn list next'. If your version falls within the vulnerable range, inspect server logs for unusual path traversal attempts or requests containing encoded backslashes.

Impact Analysis

An attacker could exploit this to access sensitive build data and encryption keys, potentially leading to remote code execution in your application. This could compromise the entire system if the attacker gains control.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. Non-compliance may result in legal penalties and reputational damage.

Mitigation Strategies

Upgrade Next.js to version 15.5.24 or 16.3.3 or later immediately. If upgrading is not possible, disable the incremental cache feature or restrict server access to trusted sources. Review and remove any exposed build data or encryption keys from cache directories.

Hi! I’m here to help you understand CVE-2026-75604. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70