Cross-site Request Forgery (CSRF) Affecting next package, versions >=16.0.1 <16.1.7>=16.2.0-canary.0 <16.2.0-canary.102
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Cross-site Request Forgery (CSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-NEXT-15674557
- published17 Mar 2026
- disclosed17 Mar 2026
- creditUnknown
Introduced: 17 Mar 2026
NewCVE-2026-27978 (opens in a new tab)How to fix?
Upgrade next to version 16.1.7, 16.2.0-canary.102 or higher.
Overview
next is a react framework.
Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) due to the uncaught origin: null in the Server Action CSRF validation. An attacker can perform unauthorized state-changing actions on behalf of a user by inducing the user's browser to submit requests from a sandboxed context, bypassing origin verification.
Workaround
This vulnerability can be mitigated by adding CSRF tokens for sensitive Server Actions, preferring SameSite=Strict on sensitive authentication cookies, and ensuring that null is not allowed in serverActions.allowedOrigins unless intentionally required and additionally protected.