Bug 2573971 (CVE-2026-119348)

Summary: CVE-2026-119348 next: Next.js: Information disclosure via HTTP response desynchronization
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bbrownin, chfoley, eborisov, jturenov, kaycoth, lball, ngough, rhel-process-autobot, swoodman, veshanka, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Next.js. When returning upstream responses through App Router route handlers or the fetch cache, the application can emit an HTTP response whose declared framing does not match the actual body sent. When deployed behind an HTTP reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. This issue allows an attacker to cause information disclosure by exposing another client's response or inject arbitrary responses into other client queues.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-16 21:52:27 UTC
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.