Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker may abuse path handling in affected Next.js applications hosted on Windows to access private build data. Exposure of a server encryption key can then enable application-level remote code execution. The attack is rated critical, although the supplied sources do not establish active exploitation.
Executive priority
Treat affected internet-facing Windows applications as an urgent patching priority because successful exploitation can progress from sensitive build-data disclosure to remote code execution. First identify Windows-hosted Next.js deployments and their router configuration, then upgrade within an emergency change window. Active exploitation is not established by the supplied evidence.
Technical view
Next.js fails to consistently escape backslashes in route segments before creating incremental-cache paths on Windows. Encoded Windows separators can permit traversal beyond the cache root and disclosure of build artifacts, including the server-reference-manifest encryption key. Affected configurations use Pages Router or App Router without Cache Components. Exploitation has high complexity but potentially severe confidentiality, integrity, and availability impact.
Likely exposure
Potentially exposed systems are Windows-hosted Next.js applications running 13.4.0 through 15.5.23, or 16.0.0 through 16.3.2, with Pages Router or App Router without Cache Components. Internet-accessible applications face the clearest remote attack surface. Other platforms and configurations are not identified as affected in the supplied sources.
Exploitation context
The CVSS 3.1 score is 9.0: network-accessible, unauthenticated, no user interaction, high attack complexity, and changed scope. The source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation. Key disclosure can enable code execution, but the sources do not describe observed attacks or exploit availability.
Researcher notes
The vulnerable logic is identified in escape-path-delimiters.ts and file-system-cache.ts. The security boundary failure is CWE-22 path traversal caused by inconsistent handling of encoded Windows separators. The reported impact is a chain: traversal, private build-data disclosure, encryption-key exposure, then possible remote code execution. The supplied sources do not provide safe detection indicators or confirm exploit reliability.
Mitigation direction
- Upgrade affected 15.x deployments to Next.js 15.5.24 or later.
- Upgrade affected 16.x deployments to Next.js 16.3.3 or later.
- Prioritize internet-facing Windows deployments using an affected router configuration.
- Review the vendor advisory for any additional incident-response or deployment guidance.
Validation and detection
- Inventory Next.js versions and confirm whether application servers run on Windows.
- Determine whether each application uses Pages Router or App Router without Cache Components.
- Confirm deployed versions are at least 15.5.24 or 16.3.3, as applicable.
- Review available telemetry for unexpected access to private build or incremental-cache data.
- If exposure is suspected, assess possible server-reference-manifest key disclosure using established incident-response procedures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75604 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/vercel/next.js/commit/968b9fcb26bdeb8e0a861a9df05361474666d51bCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vercel/next.js/commit/b0f3460a92b955d3ca41fccff9a525a2b910fbf3CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v15.5.24CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v16.3.3CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.