Dev WebSocket hijacking via null-Origin bypass
Published Mar 17, 2026 · Updated Mar 18, 2026
Missing WebSocket origin validation in Next.js 16.0.1 through 16.1.6 allows remote attackers to read and alter HMR traffic. The development router skips parsing and allowlist validation when the Origin header equals null, allowing opaque or sandboxed browser contexts to reach the HMR channel. Exploitation requires a developer to visit attacker-controlled content while an affected next dev server is reachable and allowedDevOrigins is configured; next start is unaffected.
Summary
What happened
Missing WebSocket origin validation in Next.js 16.0.1 through 16.1.6 allows remote attackers to read and alter HMR traffic. The development router skips parsing and allowlist validation when the Origin header equals null, allowing opaque or sandboxed browser contexts to reach the HMR channel. Exploitation requires a developer to visit attacker-controlled content while an affected next dev server is reachable and allowedDevOrigins is configured; next start is unaffected.
The record
- CVE
- CVE-2026-27977
- Published
- Mar 17, 2026
- Updated
- Mar 18, 2026
- Vendor
- Vercel
- Product
- Next.js
- Classifications
- CWE-1385, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 16.0.1, < 16.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo