CVE-2026-44578

HIGHPre-NVD 8.68.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.7 because EPSS predicts 39% probability of exploitation within the next 30 days (top 1.5% of all CVEs). a secondary CVSS source baseline 8.6 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, secondary
Elevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 39%CVSS: 8.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.6
EG Score
8.7(high)
EG Risk
70(Track)
EG Risk 70/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
39%
EPSS %ILE
99%
KEV
Not listed

Published

May 13, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. Sources: github.
github Patch Available

Server-side request forgery in applications using WebSocket upgrades · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r

Vendor Advisories for CVE-2026-44578(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnext2026-08-12redhat
redhatrhtas/rekor-search-ui-rhel9:17839586222026-07-16redhat
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
next—16.2.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-11 08:23 UTCOSV refresh
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-23 17:51 UTCEG score recompute
  17. 2026-08-23 17:51 UTCVendor advisory
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 19:48 UTCEG score recompute
  22. 2026-08-20 19:48 UTCVendor advisory
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 10:39 UTCEG score recompute
Show 75 more
  1. 2026-08-17 10:39 UTCVendor advisory
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 04:03 UTCEG score recompute
  4. 2026-08-16 04:03 UTCVendor advisory
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-15 00:29 UTCVendor advisory
  8. 2026-08-14 13:32 UTCVendor advisory
  9. 2026-08-14 02:32 UTCEG score recompute
  10. 2026-08-14 02:32 UTCVendor advisory
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 13:38 UTCEG score recompute
  13. 2026-08-13 13:38 UTCVendor advisory
  14. 2026-08-13 12:28 UTCEG score recompute
  15. 2026-08-13 12:28 UTCVendor advisory
  16. 2026-08-13 02:47 UTCVendor advisory
  17. 2026-08-12 15:50 UTCEG score recompute
  18. 2026-08-12 15:50 UTCVendor advisory
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-11 15:28 UTCEG score recompute
  21. 2026-08-11 15:28 UTCVendor advisory
  22. 2026-08-11 00:57 UTCVendor advisory
  23. 2026-08-10 11:30 UTCVendor advisory
  24. 2026-08-09 23:51 UTCVendor advisory
  25. 2026-08-09 12:54 UTCVendor advisory
  26. 2026-08-09 01:55 UTCVendor advisory
  27. 2026-08-08 04:53 UTCVendor advisory
  28. 2026-08-07 17:56 UTCEG score recompute
  29. 2026-08-07 17:56 UTCVendor advisory
  30. 2026-08-07 06:59 UTCVendor advisory
  31. 2026-08-06 19:34 UTCEG score recompute
  32. 2026-08-06 19:34 UTCVendor advisory
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 08:38 UTCVendor advisory
  35. 2026-08-05 21:40 UTCEG score recompute
  36. 2026-08-05 21:40 UTCVendor advisory
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-04 10:38 UTCEPSS rescore
  39. 2026-08-04 06:07 UTCVendor advisory
  40. 2026-08-03 19:09 UTCVendor advisory
  41. 2026-08-02 19:08 UTCVendor advisory
  42. 2026-08-02 08:11 UTCEG score recompute
  43. 2026-08-02 08:11 UTCVendor advisory
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 19:51 UTCEG score recompute
  46. 2026-08-01 19:51 UTCVendor advisory
  47. 2026-08-01 04:16 UTCEPSS rescore
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 03:15 UTCEG score recompute▲ 0.10
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-20 17:08 UTCEPSS rescore
  59. 2026-07-19 02:29 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 02:29 UTCOSV refresh
  62. 2026-07-16 17:03 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-13 22:30 UTCEPSS rescore
  66. 2026-07-13 06:13 UTCEPSS rescore
  67. 2026-07-12 05:46 UTCEPSS rescore
  68. 2026-07-11 08:27 UTCEPSS rescore
  69. 2026-07-09 19:10 UTCEPSS rescore
  70. 2026-07-06 16:27 UTCEPSS rescore
  71. 2026-07-05 02:30 UTCEPSS rescore
  72. 2026-07-01 15:07 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-29 14:06 UTCEPSS rescore
  75. 2026-06-28 04:56 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdinosn/CVE-2026-44578
    First seen May 16, 2026

    CVE-2026-44578: Next.js WebSocket Upgrade SSRF — pre-auth credential theft via localhost:80. Lab + exploit + audit.

    Open source ↗
  • GitHub PoCynsmroztas/nextssrf
    First seen May 15, 2026

    NextSSRF — CVE-2026-44578 Scanner & Exploit ║ ║ Next.js WebSocket Upgrade Handler SSRF

    Open source ↗
  • GitHub PoClove07oj/nextjs-cve-2026-44578
    First seen May 15, 2026

    Nuclei templates for detecting CVE-2026-44578 (Next.js WebSocket Upgrade SSRF) with multi-cloud metadata validation, Next.js fingerprinting, and real-world scanning workflows. Includes references to the original NextSSRF research and exploit tooling.

    Open source ↗
  • Nucleijavascript/cves/2026/CVE-2026-44578.yaml
    First seen Jan 1, 2026

    Next.js WebSocket Upgrade Handler - SSRF

    Open source ↗

Frequently asked(5)

What is CVE-2026-44578?
CVE-2026-44578 is a high vulnerability published on May 13, 2026. 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…
When was CVE-2026-44578 disclosed?
CVE-2026-44578 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44578 actively exploited?
CVE-2026-44578 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39% probability of exploitation in the next 30 days, which ranks it in the top 1.5% of all scored CVEs.
What is the CVSS score of CVE-2026-44578?
CVE-2026-44578 has a CVSS v3 base score of 8.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2026-44578?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44578, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44578

Explore →

Is Your Infrastructure Affected by CVE-2026-44578?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs