Skip to content
Threat Brief

← All advisories

CVE-2026-119348

Medium 6.3No known exploitationFix available

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

Vendor advisory: GHSA-pc58-hwjq-p385

Record last updated

CVSS score

6.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 23% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-444

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
npmnextfrom 16.0.0 up to and including 16.4.416.4.5GitHub Advisory Database
npmnextall versions up to and including 15.5.2815.5.29GitHub Advisory Database
vercelnext.js< 15.5.29Not documentedCVE Program
vercelnext.js>= 16.0.0, < 16.4.5Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references