CVE-2026-119346: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
Affects nextSource GCVE Database
Not known to be exploited · CVSS 6.0 Medium : upgrade to 15.5.29 when convenient.
Data as of 19 Nov 2026, 23:07 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.0 |
|---|
- Patch
- Available – fixed in 15.5.29, 16.4.5
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 19 Nov 2026.
What to do
Upgrade next to 15.5.29; next to 16.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnext | Affected
| Fixed in
|
| npmnext | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Next.js to version 15.5.29 or later in the 15.x series, or 16.4.5 or later in the 16.x series, where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the root cause.
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 HttpOnly cookies set via NextResponse on Edge runtime routes are exposed through an internal response header. This header duplicates the cookie value and attributes, making sensitive HttpOnly cookies accessible to JavaScript on the same origin. This issue affects App Router route handlers and Pages Router Edge API routes. A fix is available 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)
- nvd.nist.gov/vuln/detail/CVE-2026-119346 (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 (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)