CVE-2026-48779

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

June 15, 2026

Last Modified

September 11, 2026

Advisory Details (5)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Memory exhaustion DoS from tiny fragments and data chunks · Advisory · websockets/ws · GitHub

https://github.com/websockets/ws/security/advisories/GHSA-96hv-2xvq-fx4p
github_commit Patch Available

commit fd36cd864fcd (websockets/ws)

Patch available: websockets/ws 7.5.11 (contains commit fd36cd864fcd)

https://github.com/websockets/ws/commit/fd36cd864fcdf62a08273a99e19a7d975401fee8
github_commit Patch Available

commit bca91adf1567 (websockets/ws)

Patch available: websockets/ws 8.21.0 (contains commit bca91adf1567)

https://github.com/websockets/ws/commit/bca91adf15677e47dbe4f959653452727be28b94
github_commit Patch Available

commit b5372ac67bb9 (websockets/ws)

Patch available: websockets/ws 5.2.5 (contains commit b5372ac67bb9)

https://github.com/websockets/ws/commit/b5372ac67bb97a773727b8e9f5035a8123556d53
github_commit Patch Available

commit 86d3e8a5fb02 (websockets/ws)

Patch available: websockets/ws 6.2.4 (contains commit 86d3e8a5fb02)

https://github.com/websockets/ws/commit/86d3e8a5fb0246ed373860c5fbb0de88824a27f7

Vendor Advisories for CVE-2026-48779(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatws2026-09-10redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-132026-07-29redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat
redhatdevspaces/dashboard-rhel9:17824987922026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17828394942026-07-01redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat
redhatopenshift-service-mesh/kiali-rhel9:17822015372026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018332026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel8:17822875802026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018122026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822014662026-06-29redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatdotnet9-0-main-9.0.118-1.hum12026-06-19redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-ws7.4.2+~cs18.0.8-2 ... 8.8.1+~cs13.7.3-1 (17 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-ws8.11.0+~cs13.7.3-1 ... 8.21.3+~cs14.19.1-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ws8.18.1+~cs14.18.2-1 ... 8.21.3+~cs14.19.1-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ws8.18.1+~cs14.18.2-1, 8.19.0+~cs14.19.1-1, 8.20.1+~cs14.19.1-18.21.0+~cs14.19.1-1—
npm(1)
PackageVulnerable rangeFixed inDependents
ws—8.21.0—

Weakness Classification(3)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 80× 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 287 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48779?
CVE-2026-48779 is a high vulnerability published on June 15, 2026. ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally…
When was CVE-2026-48779 disclosed?
CVE-2026-48779 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48779 actively exploited?
CVE-2026-48779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48779?
CVE-2026-48779 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48779, 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-48779

Explore →

Is Your Infrastructure Affected by CVE-2026-48779?

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

Start Free Scan →Browse All CVEs