Skip to main content
VulnerabilityPublished

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

Affects nextSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119346· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 15.5.29 when convenient.

Data as of 19 Nov 2026, 23:07 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.0
Patch
Available – fixed in 15.5.29, 16.4.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade next to 15.5.29; next to 16.4.5.

Affected software

ProductAffectedFixed in
npmnextAffected
  • >=15.0.0 <15.5.29
Fixed in
  • 15.5.29
npmnextAffected
  • >=16.0.0 <16.4.5
Fixed in
  • 16.4.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Next.js to version 15.5.29 or later in the 15.x series, or 16.4.5 or later in the 16.x series, where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the root cause.

Description

Next.js versions from 15.0.0 up to but not including 15.5.29, and from 16.0.0 up to but not including 16.4.5, have a vulnerability where HttpOnly cookies set via NextResponse on Edge runtime routes are exposed through an internal response header. This header duplicates the cookie value and attributes, making sensitive HttpOnly cookies accessible to JavaScript on the same origin. This issue affects App Router route handlers and Pages Router Edge API routes. A fix is available in versions 15.5.29 and 16.4.5.

References

Community reviews

Loading reviews…