Skip to main content
CVE-2026-119348VulnerabilityPublished

Next.js: Cross-client response injection and disclosure

Affects nextSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119348· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.4.5 when convenient.

Data as of 19 Nov 2026, 23:07 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.3
Patch
Available – fixed in 16.4.5, 15.5.29
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade next to 16.4.5; next to 15.5.29.

Affected software

ProductAffectedFixed in
npmnextAffected
  • >=16.0.0 <16.4.5
Fixed in
  • 16.4.5
npmnextAffected
  • <15.5.29
Fixed in
  • 15.5.29

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading Next.js to versions 16.4.5 or later, or 15.5.29 or later. Applying these fixed versions fully mitigates the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in self-hosted Next.js applications using App Router route handlers and fetch cache can cause cross-client response injection and disclosure. This occurs when the application returns an upstream fetched response unchanged, leading to mismatched response framing. When deployed behind an HTTP/1.1 reverse proxy that allows pipelined response queueing, crafted upstream responses can desynchronize client responses, enabling injection and disclosure of other clients' data. Fixed versions 16.4.5 and 15.5.29 address this issue.

References

Community reviews

Loading reviews…