Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
GHSA-f3mh-rxg3-f5g2 · CVE-2026-119346
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Next.js applications that set cookies through NextResponse on Edge runtime routes — App Router route handlers and Pages Router Edge API routes — send an internal x-middleware-set-cookie header in the public response, duplicating the cookie value and its attributes. This makes HttpOnly cookies, such as session tokens, readable by JavaScript running on the same origin when an application sets a sensitive cookie on an affected response.
References
- WEB https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-119346
- WEB https://github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2
- WEB https://github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29
- PACKAGE https://github.com/vercel/next.js
- WEB https://github.com/vercel/next.js/releases/tag/v15.5.29
- WEB https://github.com/vercel/next.js/releases/tag/v16.4.5
- WEB https://nextjs.org/blog/november-2026-security-release
Ready to move
Start Securing
Free, no credit card | First findings in minutes