CVE-2026-75604
Next.js path-traversal exposes cache keys, enabling RCE on Windows-hosted apps.
WAF coverage: Path traversal. WAF catches `../` patterns.
Also consider: canonical path validation
Is CVE-2026-75604 being exploited?
Not confirmed. CVE-2026-75604 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.5% probability of exploitation in the next 30 days.
How severe is CVE-2026-75604?
CVE-2026-75604 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-75604?
Yes. A fix has been recorded for CVE-2026-75604. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75604 affect?
CVE-2026-75604 affects Next.js >=13.4.0 and <15.5.24, Next.js 16.x <16.3.3, Apps using Pages Router or App Router on Windows without Cache Components. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75604?
Upgrade to Next.js 15.5.24 or 16.3.3, rotate exposed keys, and audit Windows deployments.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Encoded backslashes allow path traversal to expose server-reference-manifest encryption key, enabling remote code execution in affected Next.js apps.
Immediate action required
- affected>= 13.4.0 and < 15.5.24
- affected>= 16.0.0 and < 16.3.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.