Summary
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
next to 15.5.29 or later; next to 16.4.5 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-119346? CVE-2026-119346 is a medium-severity security vulnerability in next (npm), affecting versions >= 15.0.0, <= 15.5.28. It is fixed in 15.5.29, 16.4.5.
- Which versions of next are affected by CVE-2026-119346? next (npm) versions >= 15.0.0, <= 15.5.28 is affected.
- Is there a fix for CVE-2026-119346? Yes. CVE-2026-119346 is fixed in 15.5.29, 16.4.5. Upgrade to this version or later.
- Is CVE-2026-119346 exploitable, and should I be worried? Whether CVE-2026-119346 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-119346 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-119346?
- Upgrade
nextto 15.5.29 or later - Upgrade
nextto 16.4.5 or later
- Upgrade