CVE-2026-119348

Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses

Published Nov 16, 2026 CVSS 4.0 · 6.3 Medium EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

This vulnerability in self‑hosted Next.js allows a malicious upstream response to be inserted into or disclosed from another client's response stream. The flaw arises when route handlers or the fetch cache return a fetched upstream response unchanged, causing the declared framing to mismatch the actual body when the application sits behind an HTTP/1.1 reverse proxy that supports pipelined queues. Because the response framing differs, a crafted upstream payload can desynchronize the client queues, leading to injection of forged responses or inadvertent leakage of relative client data. The weakness is classified as CWE‑444: Response Injection, providing a pathway for an attacker to manipulate cross‑client HTTP responses without authentication or privilege escalation.

Affected Systems

Vercel’s Next.js framework, specifically self‑hosted deployments of the App Router route handlers and fetch cache before version 15.5.29 and 16.4.5, are affected. Any next.js app running in those versions and exposed to an HTTP/1.1 reverse proxy that allows pipelining is vulnerable; older or patched versions are not.

Risk and Exploitability

The CVSS score of 6.3 indicates medium severity. Because the EPSS score is not available and the issue is not listed in the CISA KEV catalog, direct exploitation data is limited, but the attack path is clear: an attacker must control or influence an upstream response that travels through the application, and the application must be behind a reverse proxy permitting request pipelining. Once these conditions are met, the attacker can inject crafted headers and body content into the next client in the pipeline or read data intended for another client, thereby achieving information disclosure or tampering with client traffic. The risk is therefore contingent on the presence of the specific proxy configuration.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Next.js to version 15.5.29, 16.4.5, or later.
  • If upgrading is not immediately possible, reconfigure the HTTP/1.1 reverse proxy to disable pipelining or switch to an HTTP/2 implementation, where queued responses are not interleaved.
  • Validate and sanitize any responses returned from upstream services before passing them back to clients, ensuring the framing and body content match.

Generated by OpenCVE AI on November 16, 2026 at 19:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
Description 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.
Title Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
Weaknesses CWE-444
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:43 PM
Reserved
Oct 29, 2026, 8:44 PM
Status
Awaiting Analysis
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 8:37 PM