CVE-2026-27977
Next.js is a React framework for building full-stack web …
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, in `next dev`, cross-site protection for internal websocket endpoints could treat `Origin: null` as a bypass case even if `allowedDevOrigins` is configured, allowing privacy-sensitive/opaque contexts (for example sandboxed documents) to connect unexpectedly. If a dev server is reachable from attacker-controlled content, an attacker may be able to connect to the HMR websocket channel and interact with dev websocket traffic. This affects development mode only. Apps without a configured `allowedDevOrigins` still allow connections from any origin. The issue is fixed in version 16.1.7 by validating `Origin: null` through the same cross-site origin-allowance checks used for other origins. If upgrading is not immediately possible, do not expose `next dev` to untrusted networks and/or block websocket upgrades to `/_next/webpack-hmr` when `Origin` is `null` at the proxy.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vercel/next.js/commit/862f9b9bb41d235e0d8cf44aa811e7fd118cee2a
- github.com/vercel/next.js/releases/tag/v16.1.7
- github.com/vercel/next.js/security/advisories/GHSA-jcc7-9wpm-mj36
- nvd.nist.gov/vuln/detail/CVE-2026-27977
- github.com/advisories/GHSA-jcc7-9wpm-mj36
- nvd.nist.gov/vuln/detail/CVE-2026-27977
- cve.org/CVERecord?id=CVE-2026-27977
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.