home / blog

2026-11-20 · medium

CVE-2026-119348: Desynchronization Vulnerability in Next.js

Next.js vulnerability causes data disclosure between clients through response desynchronization.

CVE-2026-119348: Desynchronization Vulnerability in Next.js

CVE-2026-119348 is a vulnerability in Next.js that affects self-hosted App Router route handlers. When these route handlers emit an unfetched upstream response and the application is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, response desynchronization between clients can occur. This can lead to response injection into another client's queue or disclosure of another client's responses.

The vulnerability has a CVSS score of 6.3 classified as medium severity. It was officially published on the National Vulnerability Database (NVD) on November 16, 2026. Recent signals indicate the presence of a public Proof of Concept (PoC) on GitHub, demonstrating how to exploit this vulnerability for cross-client response injection/disclosure attacks.

For defense, it is essential to promptly apply updates to patched versions 15.5.29 or 16.4.5 of Next.js. For applications that cannot be immediately updated, it is recommended to verify the configuration of reverse proxies used, ensuring they do not permit pipelined response queueing. It is also important to monitor anomalous activity in Next.js applications, particularly to detect exploitation attempts of this vulnerability.

At a glance

What
Response desynchronization vulnerability in self-hosted Next.js App Router route handlers that can cause response injection between clients or data disclosure.
Severity
Medium (CVSS 6.3)
Affected versions
Prior to 15.5.29 and 16.4.5
Fix
Update to versions 15.5.29 or 16.4.5
Status
Published on NVD on 2026-11-16
Action
Apply patches and verify absence of reverse proxies that permit pipelined response queueing

Sources: NVD, CVE-2026-119348

← All articles