Skip to main content
VulnerabilityPublished

CVE-2026-119346: vercel next.js · Information Exposure

Affects vercel next.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 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.0Medium
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.0
Patch
Available – fixed in 16.4.5, 15.5.29
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/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.0.0 <15.5.29
Fixed in
  • 15.5.29

AI-suggested

Upgrade Next.js to version 15.5.29 or later if using the 15.x branch, or to version 16.4.5 or later if using the 16.x branch. These versions contain the fix that prevents the x-middleware-set-cookie header from being exposed in public responses. No additional mitigation steps are indicated by the vendor advisory.

Description

Next.js versions from 15.0.0 up to but not including 15.5.29, and from 16.0.0 up to but not including 16.4.5, have a vulnerability where the internal x-middleware-set-cookie header is exposed in public responses on Edge runtime routes. This header duplicates cookie values and attributes, allowing JavaScript on the same origin to read HttpOnly cookies, including sensitive session tokens. This issue affects both App Router route handlers and Pages Router Edge API routes. The vulnerability is fixed in versions 15.5.29 and 16.4.5.

References

Community reviews

Loading reviews…