CVE-2026-119346: medium-severity vulnerability in vercel next.js
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6epss 0.3%
Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.29 and 16.4.5, Next.js applications that use NextResponse to set cookies on Edge runtime routes expose the internal x-middleware-set-cookie header in the public response. This affects App Router route handlers and Pages Router Edge API routes. The header duplicates each cookie value and its attributes, so JavaScript already running on the same origin can read values that the Set-Cookie header marks HttpOnly, including sensitive session tokens set on an affected response. This issue is fixed in versions 16.4.5 and 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
Affected products
vercel · next.jsRelated CVEs — vercel next.js
In the same product, most dangerous first.
CVE-2025-29927CRITICALAuthorization Bypass in Next.js MiddlewareEPSS 99.2%CVE-2024-46982HIGHCache Poisoning in next.jsEPSS 61.0%CVE-2021-43803HIGHUnexpected server crash in Next.jsEPSS 47.3%CVE-2026-44578HIGHNext.js: Server-side request forgery in applications using WebSocket upgradesEPSS 35.5%CVE-2024-34351HIGHNext.js Server-Side Request Forgery in Server ActionsEPSS 5.5%CVE-2024-51479HIGHAuthorization bypass in Next.jsEPSS 4.0%
References
https://github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2https://github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29https://github.com/vercel/next.js/releases/tag/v15.5.29https://github.com/vercel/next.js/releases/tag/v16.4.5https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2https://nextjs.org/blog/november-2026-security-release