vercel · Next.js · published 2026-03-18
CVE-2026-29057Next.js: HTTP request smuggling in rewrites
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-29057 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This Next.js vulnerability: CVSS 6.3 (v4.0), attacks can be automated. Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13.
Patch events
Web frameworkNext.js
Next.js security releases: 16.1.7, 15.5.14, 15.5.13
Upgrade to
16.1.715.5.1415.5.13Why: Vendor security release for server software (most severe: CVE-2026-27979).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (43th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 16.0.0-beta.0, < 16.1.7(affected)>= 9.5.0, < 15.5.13(affected)
Description (from the CVE record)#
Next.js is a React framework for building full-stack web applications. Starting in version 9.5.0 and prior to versions 15.5.13 and 16.1.7, when Next.js rewrites proxy traffic to an external backend, a crafted `DELETE`/`OPTIONS` request using `Transfer-Encoding: chunked` could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes. An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel. The vulnerability originated in an upstream library vendored by Next.js. It is fixed in Next.js 15.5.13 and 16.1.7 by updating that dependency’s behavior so `content-length: 0` is added only when both `content-length` and `transfer-encoding` are absent, and `transfer-encoding` is no longer removed in that code path. If upgrading is not immediately possible, block chunked `DELETE`/`OPTIONS` requests on rewritten routes at the edge/proxy, and/or enforce authentication/authorization on backend routes.
Quoted from the CVE Program record.