CVE-2026-44578: WebSocket Upgrade SSRF in Self-Hosted Next.js
CVE-2026-44578 is a server-side request forgery vulnerability in the WebSocket upgrade handling of the built-in Next.js Node.js server. Crafted upgrade requests can cause a vulnerable server to proxy requests to arbitrary internal or external destinations because upgrade handling lacks the safety checks applied to standard HTTP requests. Affected versions begin at 13.4.13, with fixes available in 15.5.16 and 16.2.5 for their respective release lines. The issue affects self-hosted deployments; Vercel-hosted deployments are not affected. Exploitation may expose internal services and cloud metadata endpoints.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Attackers can use the Next.js server as a proxy to reach destinations accessible from the server's network environment, potentially bypassing external network restrictions. Reachable internal services, unprotected administrative interfaces, and cloud metadata endpoints may disclose sensitive information, including temporary IAM credentials, API tokens, and deployment secrets. These disclosure outcomes depend on destination reachability and the protections applied by the destination services.
Mitigation
If you can’t patch tonight, do this now.
If upgrading immediately is not possible, avoid exposing the origin server directly to untrusted networks. Block unnecessary WebSocket upgrade requests at the reverse proxy or load balancer. Restrict origin-server outbound traffic, particularly access to cloud metadata services and unrelated internal networks.
Remediation
Patch, then assume compromise.
Upgrade to Next.js 15.5.16 or later in the 15.x release line, or 16.2.5 or later in the 16.x release line. The fixes apply safety checks to WebSocket upgrade handling and permit proxying only when routing configurations explicitly identify safe external rewrites.
Exploits
7 exploits validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
References
Frequently asked questions
- Is CVE-2026-44578 exploited in the wild?
- As of Oct 3, 2026, Mallory has no reports of CVE-2026-44578 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-44578?
- Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2026-44578, the earliest disclosed May 15, 2026.
- Is there a patch for CVE-2026-44578?
- Upgrade to Next.js 15.5.16 or later in the 15.x release line, or 16.2.5 or later in the 16.x release line. The fixes apply safety checks to WebSocket upgrade handling and permit proxying only when routing configurations explicitly identify safe external rewrites.
- How severe is CVE-2026-44578?
- CVE-2026-44578 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 35.5% (98th percentile) as of Oct 3, 2026.
Recent activity
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.