next
Affected
- introduced
16.0.1, fixed16.1.7(semver)
Fixed versions
16.1.7
Fix
- Fixed version
16.1.7npm install [email protected]
Advisory
Also known as: CVE-2026-27977
Next.js: null origin can bypass dev HMR websocket CSRF checks
Summary
In next dev, cross-site protections for internal development endpoints could treat Origin: null as a bypass case even when `allowedDevOrigins` is configured. This could allow privacy-sensitive or opaque browser contexts, such as sandboxed documents, to access privileged internal dev-server functionality unexpectedly.
Impact
If a developer visits attacker-controlled content while running an affected next dev server with `allowedDevOrigins` configured, attacker-controlled browser code may be able to connect to internal development endpoints and interact with sensitive dev-server functionality that should have remained blocked.
This issue affects development mode only. It does not affect next start, and it does not expose internal debugging functionality to the network by default.
Patches
Fixed by validating Origin: null through the same cross-site origin-allowance checks used for other origins on internal development endpoints.
Workarounds
If upgrade is not immediately possible:
next dev to untrusted networks.Origin: null for internal dev endpoints at your proxy.Low Basis: The source's own band: LOW
16.0.1, fixed 16.1.7 (semver)16.1.7
16.1.7npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0