Next.js: HttpOnly cookies can be exposed through an internal response header on Edge runtime routes
Say this is wrong
I keep which words you mean and your note, for 90 days at the most, and not your address or anything about your device.
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- next (npm): from 15.0.0, before 15.5.29
- next (npm): from 16.0.0, before 16.4.5
The fix
next (npm) fixed in 15.5.29
npmnpm install next@15.5.29pnpmpnpm add next@15.5.29yarnyarn add next@15.5.29bunbun add next@15.5.29Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.5.29 or the nearest later release, to fix CVE-2026-119346. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.next (npm) fixed in 16.4.5
npmnpm install next@16.4.5pnpmpnpm add next@16.4.5yarnyarn add next@16.4.5bunbun add next@16.4.5Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 16.4.5 or the nearest later release, to fix CVE-2026-119346. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
The advisory says an attacker can get at HttpOnly cookie values through an internal response header on Next.js Edge runtime routes. The flaw sits in the `next` npm package, and the record lists fixed releases 15.5.29 and 16.4.5.
Teams that run the `next` npm package with Edge runtime routes. The record names versions 15.0.0, 15.5.29, 16.0.0 and 16.4.5, so whether a given install is affected depends on its own version.
Confidence: high. The record names each affected package, its versions and the release that fixes it.
Explanation written by Auto from the sources below, and checked against the facts.
Say this is wrong
I keep which words you mean and your note, for 90 days at the most, and not your address or anything about your device.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".