next
Affected
- introduced
16.0.1, fixed16.1.7(semver)
Fixed versions
16.1.7
Fix
- Fixed version
16.1.7npm install [email protected]
Advisory
Also known as: CVE-2026-27978
Next.js: null origin can bypass Server Actions CSRF checks
Summaryorigin: null was treated as a "missing" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed iframes) could bypass origin verification instead of being validated as cross-origin requests.
Impact
An attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF).
Patches
Fixed by treating 'null' as an explicit origin value and enforcing host/origin checks unless 'null' is explicitly allowlisted in experimental.serverActions.allowedOrigins.
Workarounds
If upgrade is not immediately possible:
SameSite=Strict on sensitive auth cookies.'null' in serverActions.allowedOrigins unless intentionally required and additionally protected.Medium Basis: The source's own band: MODERATE
16.0.1, fixed 16.1.7 (semver)16.1.7
16.1.7npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0