For your digest
next: Information exposure in Next.js dev server due to lack of origin verification
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
next (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- next (npm): from 15.0.0, before 15.2.2
- next (npm): from 13.0, before 14.2.30
The fix
next (npm) fixed in 15.2.2
npmnpm install next@15.2.2pnpmpnpm add next@15.2.2yarnyarn add next@15.2.2bunbun add next@15.2.2Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.2.2 or the nearest later release, to fix CVE-2025-48068. 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 14.2.30
npmnpm install next@14.2.30pnpmpnpm add next@14.2.30yarnyarn add next@14.2.30bunbun add next@14.2.30Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 14.2.30 or the nearest later release, to fix CVE-2025-48068. 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
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
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".