CVE-2026-119348
Received Received - Intake

HTTP/1.1 Response Desynchronization in Next.js

Vulnerability report for CVE-2026-119348, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
vercel next.js to 16.4.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-444 The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Next.js applications using App Router route handlers or fetch cache that return upstream responses unchanged. It occurs when the declared response framing does not match the actual body sent, potentially allowing response injection or disclosure if the app is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing. The issue is patched in versions 16.4.5 and 15.5.29.

Detection Guidance

Detecting this vulnerability requires checking if your Next.js application is running a vulnerable version (16.0.0 to 16.4.4 or 15.5.28 or lower) and if it uses App Router route handlers or the fetch cache. Inspect your application's version and configuration. No specific commands are provided in the resources to detect this vulnerability directly.

Impact Analysis

An attacker could exploit this to inject responses into another client's queue or disclose another client's response. This requires network access, high attack complexity, and specific proxy conditions but no privileges or user interaction. The impact includes low confidentiality and integrity loss for the vulnerable system.

Mitigation Strategies

Upgrade Next.js to version 16.4.5 or 15.5.29 or later to patch the vulnerability. Ensure your reverse proxy does not allow pipelined response queueing if you cannot upgrade immediately. Review and remove any custom handling of content-length, content-encoding, or transfer-encoding headers in forwarded responses.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119348. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...