Skip to content
Threat Brief

← All advisories

CVE-2026-119346

Medium 6.0No known exploitationFix available

Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes

Vendor advisory: GHSA-f3mh-rxg3-f5g2

Record last updated

CVSS score

6.0

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 23% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-200, CWE-201

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
npmnextfrom 15.0.0 up to and including 15.5.2815.5.29GitHub Advisory Database
npmnextfrom 16.0.0 up to and including 16.4.416.4.5GitHub Advisory Database

Timeline

  1. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references