Loading...
Skip to main content
GeekWala

CVE-2026-44578 — Vulnerability in next — CVE Details

HIGH

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

Published May 11, 2026Updated September 10, 2026Source: osv

Summary

### 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.

Advisory Timeline

  • First published May 11, 2026 (154 days ago).
  • Last revised September 10, 2026 — 121 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

npm
Update next to 16.2.5 or later
npm install next@16.2.5
npm
Update next to 15.5.16 or later
npm install next@15.5.16

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: npm (1).

PackageEcosystemAffectedFixed In
next
npm
All versions16.2.5
next
npm
All versions15.5.16

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-918
    Server-Side Request Forgery (SSRF)MITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

References

Frequently Asked Questions

What is CVE-2026-44578?
Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
How do I check if my project is affected by CVE-2026-44578?
CVE-2026-44578 affects next. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-44578 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.6

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-c4j6-fc7j-m34r

Related CVEs

  • CVE-2025-29927
    CRITICAL

    Authorization Bypass in Next.js Middleware

  • CVE-2026-75604
    CRITICAL

    Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

  • CVE-2026-64645
    HIGH

    Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

  • CVE-2026-107375
    HIGH

    JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort

  • CVE-2026-107384
    HIGH

    MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)

More npm advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies