Servers and applications
CVE-2026-27978
null origin can bypass Server Actions CSRF checks
- Severity
- Medium 5.3
- Published
- 16 Mar 2026
- Last changed
- 16 Mar 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 16.1.7
- Exploit chance
- 0.2% in the next 30 daysHigher than 14% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · Needs someone to view a page or file
- Attacker can
- Change some data
- CVSS vector
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- Also known as
- GHSA-mq59-m269-xvcx
- Sources
- Project advisories (GitHub)
Description
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).
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.
Affected software
| Software | Affected versions |
|---|---|
Next.jsServers and applications · github:vercel/next.js |
|
About Next.js
JavaScript framework to create web applications
- Share of all websites
- 4.0%W3Techs, Nov 2026
- Developers who used it in the past year
- 20.8%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 93,677,602npm, 15 Nov 2026
- GitHub stars
- 143,526GitHub, 15 Nov 2026
- Forks
- 32,804GitHub, 15 Nov 2026
- Latest release
- v16.4.6GitHub, 15 Nov 2026
- Released
- 9 Nov 2026GitHub
- Developer
- Vercel Inc.Wikidata
- License
- MIT LicenseWikidata
- Written in
- JavaScriptWikidata
- First released
- 25 Oct 2016Wikidata
- First published on GitHub
- 5 Oct 2016GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 16 (LTS)LTS | 16.4.6 | Yes |
| 15 (LTS)LTS | 15.5.29 | Until 31 Jan 2027 |
| 14 (LTS)LTS | 14.2.35 | Ended 26 Oct 2025 |
| 13 | 13.5.11 | Ended 21 Dec 2024 |
| 12 | 12.3.7 | Ended 21 Nov 2022 |
| 11 | 11.1.4 | Ended 27 Jan 2022 |
From endoflife.date.
Vulnerabilities in Next.js
- In our list
- 81
- Published in the last 12 months
- 59
- Critical, last 12 months
- 7
- High, last 12 months
- 19
- Known exploited
- 1
- CVE-2026-119346HttpOnly cookie exposure through internal response header on Next.js Edge runtime routesMedium 6.0 3 Nov 2026
- CVE-2026-119347SVG rejection bypass in Next.js image optimizationMedium 6.9 3 Nov 2026
- CVE-2026-119348Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responsesMedium 6.3 3 Nov 2026
- CVE-2026-119349Cross-user cache disclosure and poisoning in Next.js use cache with binary argumentsMedium 6.3 3 Nov 2026
- CVE-2026-119350Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route paramsMedium 6.3 3 Nov 2026
- CVE-2026-119351Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadataMedium 6.3 3 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-27978
- GitHub Advisory Database https://github.com/advisories/GHSA-mq59-m269-xvcx
- github.com https://github.com/vercel/next.js/security/advisories/GHSA-mq59-m269-xvcx