GHSA-c4j6-fc7j-m34r

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

At a glance

Published
Updated
CVE
CVE-2026-44578
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Description

### Impact Self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. ### Fix We now apply the same safety checks to WebSocket upgrade handling that already existed for normal HTTP requests, so upgrade requests are only proxied when routing has explicitly marked them as safe external rewrites. ### Workarounds If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks. If WebSocket upgrades are not required, block them at your reverse proxy or load balancer, and restrict origin egress to internal networks and metadata services where possible.

Affected packages

PackageVersions
npm · nextintroduced 13.4.13, fixed 15.5.16
npm · nextintroduced 16.0.0, fixed 16.2.5

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database