vercel · Next.js · published 2026-03-17

CVE-2026-27977Next.js: null origin can bypass dev HMR websocket CSRF checks

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-27977 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This Next.js vulnerability: CVSS 2.3 (v4.0). Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.1.7, 15.5.14, 15.5.13

    Upgrade to 16.1.715.5.1415.5.13

    Why: Vendor security release for server software (most severe: CVE-2026-27979).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (10th pct)FIRST EPSS v2026.06.15
CVSS base score2.3 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →