For your digest
next: Next.js: null origin can bypass Server Actions CSRF checks
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 16.0.1, before 16.1.7
The fix
next (npm) fixed in 16.1.7
npmnpm install next@16.1.7pnpmpnpm add next@16.1.7yarnyarn add next@16.1.7bunbun add next@16.1.7Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 16.1.7 or the nearest later release, to fix CVE-2026-27978. 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".