CVE
Next.js cookie value disclosure in Edge runtime responses
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 15.5.29, 16.4.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 15.5.29, 16.4.5.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Next.js applications that use NextResponse to set cookies on Edge runtime routes expose HttpOnly cookie values, including session tokens, in a public response header. An attacker can exploit this remotely without logging in, but only after a user takes some action, and then JavaScript running on the same origin can read those cookie values.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach17/20Affects Next.js (a widely deployed server, runtime, framework or database)
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 15.5.29, 16.4.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-119346 (Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-119346 (entry last updated 2026-11-16):
Affected:
- vercel next.js: from 15.0.0, fixed in 15.5.29; from 16.0.0, fixed in 16.4.5
Fixed versions: 15.5.29, 16.4.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119346 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119346 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2
- https://github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2
- https://github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29
- https://github.com/vercel/next.js/releases/tag/v15.5.29
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-119346
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119346"}.Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- vercel next.js
From 15.0.0 · fixed in 15.5.29; From 16.0.0 · fixed in 16.4.5
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119346
Is CVE-2026-119346 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-119346?
next.js: from 15.0.0 before 15.5.29; from 16.0.0 before 16.4.5.Source: cve.now feed data
How do I fix CVE-2026-119346?
Upgrade to a fixed version: 15.5.29, 16.4.5.Source: cve.now feed data