CVE-2026-119346: vercel next.js · Information Exposure
Affects vercel next.jsSource CVE Database V5
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
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.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:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
| vercelnext.js | Affected
| Fixed in
|
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
- github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2 (opens in a new tab)
- github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2 (opens in a new tab)
- github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v15.5.29 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.4.5 (opens in a new tab)
- nextjs.org/blog/november-2026-security-release (opens in a new tab)