{"id":"GHSA-ggv3-7p47-pfv8","revision":"9ae6cb3738074a56bbfb4fb59b7189d3","records":[{"revision":"9ae6cb3738074a56bbfb4fb59b7189d3","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-ggv3-7p47-pfv8","aliases":["CVE-2026-29057"],"title":"Next.js: HTTP request smuggling in rewrites","description":"## Summary\nWhen 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.\n\n## Impact\nAn 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. \n\n## Patches\nThe 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.\n\n## Workarounds\nIf upgrade is not immediately possible:\n- Block chunked `DELETE`/`OPTIONS` requests on rewritten routes at your edge/proxy.\n- Enforce authentication/authorization on backend routes per our [security guidance](https://nextjs.org/docs/app/guides/data-security).","state":0,"publishedAt":"2026-03-17T16:17:15+00:00","modifiedAt":"2026-09-10T03:50:39.2019624+00:00","affected":[{"ecosystem":"npm","name":"next","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"16.0.0-beta.0"},{"kind":"fixed","version":"16.1.7"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"next","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"9.5.0"},{"kind":"fixed","version":"15.5.13"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"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","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/vercel/next.js/security/advisories/GHSA-ggv3-7p47-pfv8","https://nvd.nist.gov/vuln/detail/CVE-2026-29057","https://github.com/vercel/next.js/commit/dc98c04f376c6a1df76ec3e0a2d07edf4abdabd6","https://github.com/vercel/next.js","https://github.com/vercel/next.js/releases/tag/v15.5.13","https://github.com/vercel/next.js/releases/tag/v16.1.7"],"sourceUrl":"https://github.com/advisories/GHSA-ggv3-7p47-pfv8","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-ggv3-7p47-pfv8","identifiers":["GHSA-ggv3-7p47-pfv8","CVE-2026-29057"]},"retained":false,"historicalAffected":[]}],"coverage":[]}