Read the docs

Next.js exposes HttpOnly cookies in internal response header

Priority MEDIUM 42CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Passive
Attack complexity
High
Attack requirements
None
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-200.

Summary

Next.js versions from 15.0.0 before 15.5.29 and from 16.0.0 before 16.4.5 are affected. Applications that use NextResponse to set cookies on Edge runtime routes copy each cookie and its attributes into the internal x-middleware-set-cookie header, which the public response exposes (CWE-200). JavaScript already running on the same origin can read cookies marked HttpOnly, including session tokens set on an affected response.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Fix Fixed next.js (vercel): 15.5.29, 16.4.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.js15.0.0 to before 15.5.29; 16.0.0 to before 16.4.515.5.29, 16.4.5Patch availableCNA
  • next.js Vendorvercel Affected 15.0.0 to before 15.5.29; 16.0.0 to before 16.4.5 Fixed in 15.5.29, 16.4.5 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*——vercel
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:* Versions — — ·vercel

Remediation

Next.js 15.5.29 and 16.4.5 fix this issue, so upgrade the 15 branch to 15.5.29 and the 16 branch to 16.4.5.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA next.js (vercel) Fixed in 15.5.29, 16.4.5

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-119346

References

  • TI-2025-34861 Unsafe deserialization in React Server Components enables RCE KEVCVSS 3.1CRITICAL 10.0
  • TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
  • TI-2024-15745 An issue in Hyper on macOS version 3.4.1 and before, allows remote attackers to execute… CVSS 3.1CRITICAL 9.8
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
  • TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
  • TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
See all 90 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences