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 48% 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 — Patch released this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
52.2%
KEV
Not listed

Published

June 15, 2026

Last Modified

July 21, 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(17)

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

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatdevspaces/dashboard-rhel9:17824987922026-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:17822014662026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018332026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel8:17822875802026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822015372026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018122026-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

(1 across 1 ecosystem)
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

(2)

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 10× in last 7d / 78× 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.

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

Related CVEs(same vendor + same CWE)

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 July 21, 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 52.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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