Read the docs

Next.js cross-client response injection and disclosure via forwarded responses

Priority MEDIUM 43CWE-444Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Self-hosted Next.js App Router route handlers and the fetch cache can emit a response whose declared framing does not match the body sent when they return a fetched upstream response unchanged (CWE-444). Behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients, injecting a response into another client's queue or disclosing another client's response. Versions before 15.5.29, and from 16.0.0 before 16.4.5, are affected. CVSS 4.0 scores it 6.3 (MEDIUM).

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

Next.js is a React framework for building full-stack web applications. Prior to 15.5.29 and 16.4.5, self-hosted Next.js App Router route handlers and the fetch cache that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When the application is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. The resulting desynchronization can inject a response into another client's queue or disclose another client's response. This issue is fixed in versions 16.4.5 and 15.5.29.

Why it matters now

Fix Fixed next.js (vercel): 15.5.29, 16.4.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.jsbefore 15.5.29; 16.0.0 to before 16.4.515.5.29, 16.4.5Patch availableCNA
  • next.js Vendorvercel Affected before 15.5.29; 16.0.0 to before 16.4.5 Fixed in 15.5.29, 16.4.5 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*——vercel
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:* Versions — — ·vercel

Remediation

Upgrade to 15.5.29 or 16.4.5, the fixed versions on each release line.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA next.js (vercel) Fixed in 15.5.29, 16.4.5

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-119348

References

  • TI-2025-34861 Unsafe deserialization in React Server Components enables RCE KEVCVSS 3.1CRITICAL 10.0
  • TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
  • TI-2024-15745 An issue in Hyper on macOS version 3.4.1 and before, allows remote attackers to execute… CVSS 3.1CRITICAL 9.8
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
  • TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
  • TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
See all 90 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences