vercel · Next.js · published 2026-03-17

CVE-2026-27978Next.js: null origin can bypass Server Actions CSRF checks

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-27978 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This Next.js vulnerability: CVSS 5.3 (v4.0). Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.1.7, 15.5.14, 15.5.13

    Upgrade to 16.1.715.5.1415.5.13

    Why: Vendor security release for server software (most severe: CVE-2026-27979).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (14th pct)FIRST EPSS v2026.06.15
CVSS base score5.3 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →