Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-29057

next.js: Next.js: HTTP request smuggling in rewrites

Overview

Published
18 Mar 2026
Modified
17 Jun 2026
Medium CVE
3 Registry packages
21 OS packages
4 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Weakness: CWE-444

Affected packages · 3

Packages affected by CVE-2026-29057
EcosystemPackageVulnerableFixed in
npm next >=16.0.0-beta.0, <16.1.7>=9.5.0, <15.5.13 16.1.715.5.13
Seal npm @seal-security/next >=16.0.6-sp1, <16.0.6-sp999 16.0.6-sp999
Seal npm next >=16.0.6-sp0, <16.0.6-sp999 16.0.6-sp999

Open a package to see all its vulnerabilities.

Operating systems · 11 fixes

Red Hat 1 release · 1 package

affected 1
aspnetcore-runtime-7-0
Red Hat fixes for CVE-2026-29057
ReleasePackageFixed in
9 aspnetcore-runtime-7-0 +11 affected

chainguard 1 release · 7 packages

fixed 7
keep jitsucom-jitsu langfuse-2 langfuse-fips-2 langfuse-fips-3 langfuse-3 +1
chainguard fixes for CVE-2026-29057
ReleasePackageFixed in
keep +1 0.51.0-r1
jitsucom-jitsu 2.11.0-r17
langfuse-2 2.95.12-r14
langfuse-fips-2 2.95.12-r17
langfuse-fips-3 3.162.0-r0
langfuse-3 3.162.0-r1

1 more row

minimos 1 release · 1 package

fixed 1
trigger-dev
minimos fixes for CVE-2026-29057
ReleasePackageFixed in
trigger-dev 4.5.0-r0

wolfi 1 release · 2 packages

fixed 2
jitsucom-jitsu langfuse-3
wolfi fixes for CVE-2026-29057
ReleasePackageFixed in
jitsucom-jitsu 2.11.0-r17
langfuse-3 3.162.0-r1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.