---
title: "GHSA-f3mh-rxg3-f5g2: Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes"
description: "Moderate severity. Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes. Affects next; fixed in 16.4.5."
url: https://inlinr.com/advisories/GHSA-f3mh-rxg3-f5g2
lang: en
---

[Packages](https://inlinr.com/packages) / [next](https://inlinr.com/packages/next) / [Security](https://inlinr.com/packages/next/security)

Moderate Vulnerability GHSA-f3mh-rxg3-f5g2 CVE-2026-119346 Published 19 Nov 2026

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

Your version 

Affected releases · [next](https://inlinr.com/packages/next)

- 16.x 16.0.0 – 16.4.4 Fixed in 16.4.5
- 15.x 15.0.0 – 15.5.28 Fixed in 15.5.29

On 16.x, the newest line:

```
npm install next@16.4.5
```

Every release on a timeline

16.x 

1. Affected

16.0.0 – 16.4.4  
47 releases
2. Fixed

16.4.5 – 16.4.6  
2 releases

15.x 

1. Affected

15.0.0 – 15.5.28  
82 releases
2. Fixed

15.5.29  
1 release

428 stable releases of next, oldest to newest, one row per major.

## What happens

Next.js applications that set cookies through `NextResponse` on Edge runtime routes — App Router route handlers and Pages Router Edge API routes — send an internal `x-middleware-set-cookie` header in the public response, duplicating the cookie value and its attributes. This makes HttpOnly cookies, such as session tokens, readable by JavaScript running on the same origin when an application sets a sensitive cookie on an affected response.

## How it is exploited

Exploitable over the network, with no account and a user to do something.

- **Confidentiality**: high
- **Integrity**: none
- **Availability**: none

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

## References

- [Reference](https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2 "https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2")  
github.com/vercel/next.js/security/advisories/G…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-119346 "https://nvd.nist.gov/vuln/detail/CVE-2026-119346")  
nvd.nist.gov/vuln/detail/CVE-2026-119346
- [Fix commit](https://github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2 "https://github.com/vercel/next.js/commit/809be725f033ec7aa4c658ba2b7a084cb039d1f2")  
809be72
- [Fix commit](https://github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29 "https://github.com/vercel/next.js/commit/9fc04bd869ded4900bed7d069832aa2c5f56fa29")  
9fc04bd
- [Package](https://github.com/vercel/next.js "https://github.com/vercel/next.js")  
github.com/vercel/next.js
- [Reference](https://github.com/vercel/next.js/releases/tag/v15.5.29 "https://github.com/vercel/next.js/releases/tag/v15.5.29")  
github.com/vercel/next.js/releases/tag/v15.5.29
- [Reference](https://github.com/vercel/next.js/releases/tag/v16.4.5 "https://github.com/vercel/next.js/releases/tag/v16.4.5")  
github.com/vercel/next.js/releases/tag/v16.4.5
- [Reference](https://nextjs.org/blog/november-2026-security-release "https://nextjs.org/blog/november-2026-security-release")  
nextjs.org/blog/november-2026-security-release

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
