CVE-2026-27978

MEDIUM

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

Title source: cna
STIX 2.1

Description

Next.js is a React framework for building full-stack web applications. Starting in version 16.0.1 and prior to version 16.1.7, `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. An attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF). This is fixed in version 16.1.7 by treating `'null'` as an explicit origin value and enforcing host/origin checks unless `'null'` is explicitly allowlisted in `experimental.serverActions.allowedOrigins`. If upgrading is not immediately possible, add CSRF tokens for sensitive Server Actions, prefer `SameSite=Strict` on sensitive auth cookies, and/or do not allow `'null'` in `serverActions.allowedOrigins` unless intentionally required and additionally protected.

Exploits (1)

github WORKING POC
by Nayekah · javascriptpoc
https://github.com/Nayekah/Next.js-Proof-of-Concept

Scores

CVSS v3 4.3
EPSS 0.0001
EPSS Percentile 0.7%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

CISA SSVC

Vulnrichment
Exploitation none
Automatable no
Technical Impact partial

Details

CWE
CWE-352
Status published
Products (3)
npm/next 16.0.1 - 16.1.7npm
vercel/next.js 16.0.1 - 16.1.7
vercel/next.js >= 16.0.1, < 16.1.7
Published Mar 18, 2026
Tracked Since Mar 18, 2026