CVE-2026-119346: Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes

Published Nov 16, 2026
·
Updated

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.

Affected Software

1 affected component
npm/next>=15.0.0<15.5.29, >=16.0.0<16.4.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.5.29
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.4.5

Event History

Nov 16, 2026
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionWeakness

Frequently Asked Questions

1

Which applications are exposed?

Applications are affected when they use NextResponse to set cookies on Edge runtime routes. The affected route types are App Router route handlers and Pages Router Edge API routes.

2

What does an attacker need to read the exposed cookie values?

JavaScript must already be running on the same origin as the affected application. It can read the publicly returned x-middleware-set-cookie header, including values for cookies marked HttpOnly.

3

How can I verify whether an endpoint is affected?

Inspect the public HTTP response from an Edge runtime route that sets cookies with NextResponse. An affected response includes x-middleware-set-cookie with duplicated cookie values and attributes.

4

What versions should be used to remediate the issue?

Upgrade Next.js to 15.5.29 or 16.4.5, which contain the fix. The affected range begins at 15.0.0 and includes affected releases before those fixes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203