Advisory

GHSA-mq59-m269-xvcx

Also known as: CVE-2026-27978

Summary

Next.js: null origin can bypass Server Actions CSRF checks

Details

Summary
origin: 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:

  • Add CSRF tokens for sensitive Server Actions.
  • Prefer SameSite=Strict on sensitive auth cookies.
  • Do not allow 'null' in serverActions.allowedOrigins unless intentionally required and additionally protected.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-17 15:30 UTC
Modified
2026-03-19 18:31 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 16.0.1, fixed 16.1.7 (semver)

Fixed versions

16.1.7

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences