Bug 2573971 (CVE-2026-119348) - CVE-2026-119348 next: Next.js: Information disclosure via HTTP response desynchronization
Summary: CVE-2026-119348 next: Next.js: Information disclosure via HTTP response desyn...
Keywords:
Status: NEW
Alias: CVE-2026-119348
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-16 21:52 UTC by OSIDB Bzimport
Modified: 2026-11-17 00:27 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.