Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-44578: Next.js is a React framework for building full-stack web applications

65
This week
HIGH 8.6REMOTEUPGRADE

CVE-2026-44578 is a high-severity flaw (CVSS 8.6) affecting next.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 deploym

Why this priority

  • High severity
  • EPSS top 2%: very likely to be exploited
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance35.5% (top 2%)
CISA exploited listNo
WeaknessCWE-918
Published2026-05-13
Last modified2026-10-26
Publisher (CNA): GitHub, Inc. · Vendor: vercel

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vercel next.js UPGRADE
Affected: >= 13.4.13 and < 15.5.16 · >= 16.0.0 and < 16.2.5
Fixed in: 15.5.16, 16.2.5
Safe to downgrade to: a release before 13.4.13
1. Check installed version
npm ls next.js
2. UPGRADE to 15.5.16
npm install next.js@">=15.5.16"
3. If no update is available yet, DOWNGRADE to a release before 13.4.13
npm view next.js versions npm install next.js@"<13.4.13"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

npm · next · FIXED · 15.5.16 · vulnerable: >= 13.4.13, < 15.5.16 · source
npm install next@">=15.5.16" npm ls next
RHEL 10 · firefox · NOT AFFECTED
RHEL 10 · thunderbird · NOT AFFECTED
RHEL 7 · firefox · NOT AFFECTED
RHEL 8 · firefox · NOT AFFECTED
RHEL 8 · thunderbird · NOT AFFECTED

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44578?

next.js: upgrade to 15.5.16, 16.2.5. Exact commands for each OS are on this page.

Is CVE-2026-44578 being exploited?

CVE-2026-44578 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44578 affect?

CVE-2026-44578 affects next.js. Severity is high (CVSS 8.6). 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 We

How urgent is CVE-2026-44578?

Priority 65/100. High severity; EPSS top 2%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities · React vulnerabilities · Next.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.