next
Affected
- introduced
16.0.0-beta.0, fixed16.1.7(semver)
Fixed versions
16.1.7
Fix
- Fixed version
16.1.7npm install [email protected]
Advisory
Also known as: CVE-2026-29057
Next.js: HTTP request smuggling in rewrites
Summary
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.
Impact
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.
Patches
The vulnerability originated in an upstream library vendored by Next.js. It is fixed 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.
Workarounds
If upgrade is not immediately possible:
DELETE/OPTIONS requests on rewritten routes at your edge/proxy.Medium Basis: The source's own band: MODERATE
16.0.0-beta.0, fixed 16.1.7 (semver)16.1.7
16.1.7npm install [email protected]9.5.0, fixed 15.5.13 (semver)15.5.13
15.5.13npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0