CVE-2026-119346
Received Received - Intake

Next.js Edge Runtime Cookie Exposure via x-middleware-set-cookie Header

Vulnerability report for CVE-2026-119346, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
vercel next.js From 15.0.0 (inc) to 15.5.29 (inc)
vercel next.js 16.4.5

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-201 The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Next.js applications using Edge runtime routes that set cookies via NextResponse. It exposes HttpOnly cookies through an internal x-middleware-set-cookie header in public responses. JavaScript running on the same origin can read these cookies, including sensitive session tokens, compromising their security.

Detection Guidance

To detect this vulnerability, inspect HTTP responses from your Next.js Edge runtime routes or App Router handlers for the presence of the x-middleware-set-cookie header. Use tools like curl to check headers: curl -I http://yourdomain.com/edge-route. If the header appears alongside Set-Cookie, the system is vulnerable.

Impact Analysis

An attacker could exploit this to read HttpOnly cookies, such as session tokens, by running JavaScript on the same origin. This could lead to session hijacking, unauthorized access to user accounts, or exposure of sensitive data stored in cookies.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's requirements for safeguarding protected health information. Organizations may face compliance violations and legal consequences if exploited.

Mitigation Strategies

Upgrade Next.js to version 16.4.5 or 15.5.29 or later. Verify the x-middleware-set-cookie header is no longer present in responses from Edge runtime routes. Test affected routes to ensure only standard Set-Cookie headers are exposed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119346. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...