Skip to main content
Public proof of conceptFix available

CVE-2026-44578

A public proof of concept exists; no exploitation attested.

  • Published2026-05-13
  • Fixed in16.2.5 · 15.5.16
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.

Timeline

dates in UTC
  1. 2026-05-1318:16CVE publishedNVD
  2. 2026-10-2523:12EPSS crossed 10 %FIRST EPSS

Versions per branch

NVD · OSV
Next.js
BranchAffectedFixed in
16.x≥ 16.0.0, < 16.2.516.2.5
15.5≥ 13.4.13, < 15.5.1615.5.16

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • vercel next.js
    Affected
    • = >= 16.0.0, < 16.2.5no fix stated
    • = >= 13.4.13, < 15.5.16no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-05-13

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @next/mdxTuxCare:npmfrom 16.0.6-tuxcare.0 · fixed in 16.0.6-tuxcare.7and 12 other packages
  • @next/mdxTuxCare:npmfrom 13.5.11-tuxcare.0 · fixed in 13.5.11-tuxcare.14and 9 other packages
  • @next/swc-linux-x64-gnuTuxCare:npmfrom 15.1.2-tuxcare.0 · fixed in 15.1.2-tuxcare.2and 1 other package
  • @rootio/nextRoot:npmall versions · fixed in 14.2.5-root.io.5
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.3
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.4
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.5
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.6

357 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-44578 Red Hat Product Security4 products fixed · 4 known affected

    Next.js: Next.js: Server-Side Request Forgery via crafted WebSocket upgrade requests

    rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · rhelai3/bootc-gaudi-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · +1 more

  • RHSA-2026:54435 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Streams for Apache Kafka 3.2.1 release and security update

  • RHSA-2026:40974 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: RHTAS 1.3.6 - Red Hat Trusted Artifact Signer Release

  • RHSA-2026:37272 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: RHTAS 1.4.2 - Red Hat Trusted Artifact Signer Release

  • RHSA-2026:34608 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Streams for Apache Kafka 2.9.4 release and security update

Full record on NVD

Fix

  1. Update Next.js to 16.2.5 · 15.5.16
  2. Vendor fix Red Hat Product Security RHSA-2026:54435 · 1 productBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2026:40974 · 1 productRed Hat Trusted Artifact Signer simplifies cryptographic signing and verifying of software artifacts such as container images, binaries and source code changes. It is a self-managed on-premise deployment of the Sigstore project available at https://sigstore.dev Platform Engineers, Software Develop…
  4. Workaround from the vendor Red Hat Product Security RHSA-2026:54435 · 1 productMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  5. No fix planned, says the vendor Red Hat Product Security CVE-2026-44578 · 4 productsWill not fix

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Published
2026-05-13
Last Modified
2026-10-26
NVD status
Modified
GitHub Advisory
GHSA-c4j6-fc7j-m34r

Frequently asked questions

What is CVE-2026-44578?

Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.

Is CVE-2026-44578 actively exploited?

Active exploitation of CVE-2026-44578 has not been confirmed. Its EPSS score was 35.5% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-44578?

CVE-2026-44578 has a CVSS v3 base score of 8.6 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.

Running Next.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record