Advisory

GHSA-c4j6-fc7j-m34r

Also known as: CVE-2026-44578

Summary

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

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-11 15:55 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 13.4.13, fixed 15.5.16 (semver)

Fixed versions

15.5.16

Fix

next

npm · All systems

Affected

  • introduced 16.0.0, fixed 16.2.5 (semver)

Fixed versions

16.2.5

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences