Vulnerability · CVE-2026-27978
Next.js is a React framework for building full-stack web applications.
Published Mar 18, 2026 · corrected/updated Jun 17, 2026 · vercel next.js · evidence confidence medium
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, 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 as an explicit origin value and enforcing host/origin checks unless is explicitly allowlisted in . If upgrading is not immediately possible, add CSRF tokens for sensitive Server Actions, prefer on sensitive auth cookies, and/or do not allow in unless intentionally required and additionally protected.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-27978 is a medium public vulnerability record for vercel next.js. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether vercel next.js is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: vercel/next.js. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 5.3. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-352. Sources contributing to this record: cve_org, nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 18, 2026 · NIST NVD
Detected
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, 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
Jun 17, 2026 · NIST NVD
Updated
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, 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
Affected
- cpe vercel/next.jsversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-27978
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2026-27978
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, was treated as a "missing" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed ifra
nvd.nist.gov