Skip to main content
VulnerabilityPublished

CVE-2026-119348: vercel next.js · HTTP Request Smuggling

Affects vercel next.jsSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 19:04 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 15 Nov 2026.

What to do

Upgrade vercel next.js to 16.4.5 or 15.5.29.

Affected software

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.0.0 <16.4.5
Fixed in
  • 16.4.5
vercelnext.jsAffected
  • <15.5.29
Fixed in
  • 15.5.29

AI-suggested

Upgrade Next.js to version 15.5.29 or later in the 15.x series, or to version 16.4.5 or later in the 16.x series, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

Next.js versions prior to 15.5.29 and between 16.0.0 and 16.4.5 contain an HTTP request smuggling vulnerability. This occurs when self-hosted Next.js App Router route handlers and the fetch cache return an upstream response whose declared framing does not match the actual body sent. When used behind an HTTP/1.1 reverse proxy that allows pipelined response queueing, this can cause response desynchronization, potentially allowing injection of responses into other clients' queues or disclosure of other clients' responses. The issue is fixed in versions 15.5.29 and 16.4.5.

References

Community reviews

Loading reviews…