<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1950087345534883&amp;ev=PageView&amp;noscript=1">
Skip to content

CVE-2026-75604: Next.js Path Traversal Enabling Remote Code Execution - What It Means for Your Business and How to Respond

Introduction

CVE-2026-75604 is a critical vulnerability in Next.js, the widely used React framework for building modern web applications. Organizations across the United States and Canada that host Next.js applications on Windows servers face elevated risk. Successful exploitation can allow an unauthenticated attacker to gain remote code execution, potentially compromising the entire application and the data it handles.

This vulnerability matters because Next.js powers customer-facing sites, internal tools, and digital services for businesses of every size. If your organization relies on these applications for revenue, customer interaction, or operations, the impact of compromise can extend far beyond a single system.

This post explains why the issue is significant, who is most at risk, the practical business consequences, real-world scenarios, and clear steps to determine whether you are affected. It then outlines how to respond effectively. Technical details appear only in the appendix for security and IT professionals.

S1 — Background & History

Vercel, the maintainer of Next.js, disclosed the vulnerability on August 25, 2026, and released patches the same day. The National Vulnerability Database published the official record on September 1, 2026. Researchers evolutionstorm and B0RI reported the issue.

The flaw affects Next.js versions from 13.4.0 up to but not including 15.5.24, and from 16.0.0 up to but not including 16.3.3. It is specific to applications running on Windows-hosted servers that use the Pages Router or the App Router without Cache Components enabled.

The vulnerability is a path traversal weakness. In plain terms, the software fails to properly handle certain path characters supplied in web requests. This allows an attacker to reach sensitive internal files that should remain protected. Disclosure of one of those files, an encryption key used by the framework, can then enable remote code execution.

It carries a CVSS 3.1 base score of 9.0, rated Critical. Public proof-of-concept code and a Metasploit module appeared quickly after disclosure. Some security researchers later observed limited exploitation activity. Fixed versions are 15.5.24 and 16.3.3. No reliable workaround exists for affected Windows deployments other than upgrading.

S2 — What This Means for Your Business

For business leaders, the core risk is straightforward. An attacker who successfully exploits this vulnerability can run arbitrary code on the server that hosts your Next.js application. That level of access can disrupt operations, expose sensitive data, and damage customer trust.

Operations may grind to a halt if the application becomes unavailable or is altered to serve malicious content. Customer accounts, transaction records, personal information, or proprietary business data stored or processed by the application can be read, modified, or stolen. Once an attacker has code execution, lateral movement into connected systems becomes possible.

Reputation damage follows quickly. Customers and partners in the United States and Canada expect organizations to protect their information. A public breach or service outage linked to an unpatched critical vulnerability can erode confidence and invite negative media coverage. Regulatory exposure is also real. Depending on the data involved, organizations may face obligations under privacy laws such as state-level requirements in the U.S. or PIPEDA in Canada, along with potential contractual and industry compliance consequences.

The combination of unauthenticated remote access and high impact means this is not a low-priority technical issue. It is a business continuity and risk-management concern that requires prompt attention from leadership and technical teams alike.

S3 — Real-World Examples

Regional Bank Online Portal: A mid-sized bank hosts its customer portal on Windows servers using an affected Next.js version. An attacker exploits the flaw, gains code execution, and accesses account data. Customers experience service disruption, regulators inquire, and the bank faces both direct remediation costs and reputational harm in its local markets.

Healthcare Provider Patient Portal: A regional healthcare network runs a patient scheduling and records interface built with Next.js on Windows. Successful exploitation exposes protected health information. The organization must notify patients, investigate the scope of access, and address potential compliance findings while restoring reliable service.

E-Commerce Retailer Product Catalog: A growing online retailer uses Next.js for its storefront on Windows infrastructure. An attacker leverages the vulnerability to alter product pages or steal customer payment-related data. Sales drop during the outage, chargebacks rise, and marketing efforts are required to rebuild trust with shoppers across the U.S. and Canada.

Professional Services Firm Client Portal: A mid-market consulting firm hosts a secure client document portal on Windows with an unpatched Next.js application. Compromise allows an attacker to access confidential client files. The firm must notify affected clients, manage contractual obligations, and invest in forensic review and system hardening.

S4 — Am I Affected?

  • You are running Next.js version 13.4.0 through 15.5.23, or 16.0.0 through 16.3.2.
  • Your Next.js application is hosted on a Windows server or Windows-based filesystem.
  • The application uses the Pages Router or the App Router without Cache Components enabled.
  • The application is reachable from the internet or from untrusted networks.
  • You have not yet upgraded to Next.js 15.5.24, 16.3.3, or a later patched release.
  • Your development or operations team has not confirmed that the running production version matches a fixed release.

If several of these statements apply, treat the application as potentially affected and prioritize verification and remediation.

Key Takeaways

  • CVE-2026-75604 is a critical vulnerability in Next.js that can enable unauthenticated remote code execution on Windows-hosted applications.
  • Businesses risk operational disruption, data exposure, reputational damage, and compliance consequences if the flaw is exploited.
  • Organizations in the United States and Canada that host customer-facing or data-sensitive Next.js applications on Windows should treat this as a high-priority issue.
  • The only reliable fix is upgrading to Next.js 15.5.24, 16.3.3, or a later secure release; no practical workaround exists for affected Windows deployments.
  • Prompt inventory of Next.js versions and hosting environments, followed by rapid patching, is the most effective response.

Call to Action

Do not leave critical web applications exposed to known remote code execution risks. IntegSec helps organizations across the United States and Canada identify vulnerabilities, validate real-world exploitability, and strengthen defenses through professional penetration testing. Contact us today to schedule an assessment and reduce your cybersecurity risk with confidence. Visit https://integsec.com.

TECHNICAL APPENDIX (security engineers, pentesters, IT professionals only)

A — Technical Analysis

The root cause is incomplete path sanitization in Next.js. Specifically, the functions in packages/next/src/shared/lib/router/utils/escape-path-delimiters.ts and packages/next/src/server/lib/incremental-cache/file-system-cache.ts do not consistently escape backslash characters in route segments before constructing incremental-cache file paths.

On Windows filesystems, backslashes serve as path separators. An attacker can supply URL-encoded Windows path separators in a remote request targeting a dynamic route. The resulting path resolves outside the intended cache root, allowing disclosure of private build artifacts, including the server-reference-manifest encryption key.

With that key, an attacker can forge encrypted Server Action payloads that lead to arbitrary code execution in the context of the Next.js process. The attack vector is network, privileges required are none, user interaction is none, and attack complexity is rated high. Scope is changed. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. The weakness is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). Official references include the NVD entry for CVE-2026-75604 and GitHub advisory GHSA-p293-qw3h-jr36.

B — Detection & Verification

Version enumeration can be performed by inspecting package.json, package-lock.json, or yarn.lock for the next dependency, or by querying the running process environment and comparing against known fixed versions 15.5.24 and 16.3.3.

Scanner signatures for CVE-2026-75604 have been added to several commercial and open-source vulnerability scanners. Log indicators may include unusual requests containing encoded backslash sequences directed at dynamic routes that trigger incremental cache operations. Behavioral anomalies include unexpected file access outside the normal cache directory or anomalous Server Action traffic following suspicious requests. Network indicators include patterns consistent with public proof-of-concept payloads that first extract build identifiers, then traverse to the server-reference-manifest, and finally submit forged Server Action requests.

C — Mitigation & Remediation

  1. Immediate (0–24h): Inventory all Next.js applications hosted on Windows. Confirm exact versions in use. If an affected version is present, schedule emergency upgrade windows and restrict external access where feasible while preparing the patch. Deploy any available WAF virtual-patch rules from providers that have published coverage.
  2. Short-term (1–7d): Upgrade all affected instances to Next.js 15.5.24 (for the 15.x line) or 16.3.3 (for the 16.x line) or later. Redeploy applications and verify the running version. Rotate the Server Actions encryption key after patching if the application was previously exposed. Review access logs for indicators of prior exploitation attempts.
  3. Long-term (ongoing): Maintain a disciplined dependency update process for Next.js and related packages. Prefer Linux-hosted environments for new deployments when operationally suitable, as the issue is Windows-specific. Enable Cache Components where architecture allows. Integrate continuous vulnerability scanning that tracks Next.js advisories. Conduct regular penetration tests focused on web application frameworks.

Official vendor patches are the primary and required remediation. No reliable interim workaround exists for Windows-hosted applications short of upgrading or taking the service offline.

D — Best Practices

  • Always sanitize and normalize path input according to the target operating system’s path semantics, explicitly handling both forward and backslash characters.
  • Enforce strict path boundary checks so that resolved filesystem paths cannot escape designated root directories.
  • Keep framework and runtime dependencies on supported, patched releases and monitor vendor security advisories closely.
  • Limit the attack surface of dynamic routes and Server Actions; avoid exposing unnecessary dynamic endpoints to untrusted networks.
  • Perform regular configuration and dependency reviews of production Next.js applications, including verification of hosting platform characteristics that affect vulnerability applicability.

Leave Comment

Want to strengthen your security posture?

Want to strengthen your organization’s security? Explore our blog insights and contact our team for expert guidance tailored to your needs.