CVE-2024-37890

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-06-17. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-1899 (ENISA EUVD) · GHSA-3h5v-q93c-6h6q (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 17, 2024

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Nov 5, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr.
GitHub commit Patch Available

commit 4abd8f6de4b0 (websockets/ws)

Patch available: websockets/ws 5.2.4 (contains commit 4abd8f6de4b0)

https://github.com/websockets/ws/commit/4abd8f6de4b0b65ef80b3ff081989479ed93377e
GitHub commit Patch Available

commit 22c28763234a (websockets/ws)

Patch available: websockets/ws 7.5.10 (contains commit 22c28763234a)

https://github.com/websockets/ws/commit/22c28763234aa75a7e1b76f5c01c181260d7917f
Web page

HTTP | Node.js v26.13.0 Documentation

https://nodejs.org/api/http.html#servermaxheaderscount
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

DoS when handling a request with many HTTP headers · Advisory · websockets/ws · GitHub

https://github.com/websockets/ws/security/advisories/GHSA-3h5v-q93c-6h6q
GitHub pull request

Fix crash when the Upgrade header cannot be read

Fix merged in websockets/ws PR #2231 on 2024-06-16 — awaiting tagged release

https://github.com/websockets/ws/pull/2231
Web page

Throws TypeError when there are too many HTTP headers · Issue #2230 · websockets/ws · GitHub

https://github.com/websockets/ws/issues/2230
GitHub commit Patch Available

commit eeb76d313e2a (websockets/ws)

Patch available: websockets/ws 6.2.3 (contains commit eeb76d313e2a)

https://github.com/websockets/ws/commit/eeb76d313e2a00dd5247ca3597bba7877d064a63
GitHub commit Patch Available

commit e55e5106f10f (websockets/ws)

Patch available: websockets/ws 8.17.1 (contains commit e55e5106f10f)

https://github.com/websockets/ws/commit/e55e5106f10fcbaac37cfa89759e4cc0d073a52c

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/rhceph-7-rhel9:17914524772026-10-15redhat
redhatopenshift-pipelines/pipelines-hub-ui-rhel8:17720364712026-03-04redhat
redhatodf4/odf-console-rhel9:v4.14.18-32025-06-04redhat
redhatodf4/odf-console-rhel9:v4.15.14-22025-06-04redhat
redhatdotnet8.0-0:8.0.113-2.el10_02025-05-13redhat
redhatdotnet6.0-0:6.0.135-2.el9_52024-11-13redhat
redhatdotnet8.0-0:8.0.110-3.el9_52024-11-13redhat
redhatrhdh/rhdh-hub-rhel9:1.3-1242024-11-11redhat
redhatodf4/odf-console-rhel9:v4.16.2-22024-09-18redhat
redhatodf4/mcg-core-rhel9:v4.16.1-22024-08-19redhat
redhatodf4/mcg-core-rhel9:v4.16.0-602024-07-17redhat
npmws @ 5.2.4 (fixes >= 2.1.0, < 5.2.4)—ghsa
npmws @ 6.2.3 (fixes >= 6.0.0, < 6.2.3)—ghsa
npmws @ 7.5.10 (fixes >= 7.0.0, < 7.5.10)—ghsa
npmws @ 8.17.1 (fixes >= 8.0.0, < 8.17.1)—ghsa

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 rangeFix by version rangeDependents
node-ws7.4.2+~cs18.0.8-2 ... 8.8.1+~cs13.7.3-1 (17 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws8.11.0+~cs13.7.3-1 ... 8.21.3+~cs14.19.1-1 (10 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws—
  • every version up to 8.18.0+~cs13.7.11-1: fixed in 8.18.0+~cs13.7.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws—
  • every version up to 8.18.0+~cs13.7.11-1: fixed in 8.18.0+~cs13.7.11-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
ws—
  • 2.1.0 up to 5.2.4: fixed in 5.2.4
  • 6.0.0 up to 6.2.3: fixed in 6.2.3
  • 7.0.0 up to 7.5.10: fixed in 7.5.10
  • 8.0.0 up to 8.17.1: fixed in 8.17.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 260 rows on record for this CVE, as 96 entries (4 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:47 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  2. 2026-11-13 01:18 UTCEchelonGraph re-scored
  3. 2026-11-13 01:18 UTCVendor advisory
  4. 2026-11-13 01:18 UTCGHSA enrichmentGHSA-3h5v-q93c-6h6q · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-12 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  6. 2026-11-11 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  7. 2026-11-10 16:38 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  8. 2026-11-09 16:31 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  9. 2026-11-08 16:36 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  10. 2026-11-07 16:36 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  11. 2026-11-06 16:32 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  12. 2026-11-05 16:34 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  13. 2026-11-05 10:28 UTCEchelonGraph re-scored
  14. 2026-11-05 10:28 UTCVendor advisory
  15. 2026-11-05 10:28 UTCGHSA enrichmentGHSA-3h5v-q93c-6h6q · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-04 16:32 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  17. 2026-11-03 16:42 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  18. 2026-11-02 16:41 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  19. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  20. 2026-11-01 08:13 UTCGHSA enrichmentGHSA-3h5v-q93c-6h6q · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 08:13 UTCEchelonGraph re-scored
  22. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  23. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  24. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  25. 2026-10-28 19:26 UTCEchelonGraph re-scored
Show 71 more
  1. 2026-10-28 19:26 UTCVendor advisory
  2. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  3. 2026-10-28 16:25 UTCOSV refresh
  4. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  5. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  6. 2026-10-25 17:07 UTCEchelonGraph re-scored
  7. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  8. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  9. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  10. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  11. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  12. 2026-10-20 19:42 UTCEchelonGraph re-scored
  13. 2026-10-20 19:42 UTCVendor advisory
  14. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  15. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  16. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  17. 2026-10-18 07:11 UTCEchelonGraph re-scored
  18. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  19. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  20. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  21. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  22. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  23. 2026-10-12 17:51 UTCEchelonGraph re-scored
  24. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  25. 2026-10-11 21:16 UTCEchelonGraph re-scored
  26. 2026-10-11 16:08 UTCEchelonGraph re-scored
  27. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  28. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  29. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  30. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  31. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  32. 2026-10-07 10:54 UTCOSV refresh
  33. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  34. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  35. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  36. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  37. 2026-09-30 19:47 UTCEchelonGraph re-scored
  38. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  39. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  40. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  41. 2026-09-27 13:44 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  42. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  43. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  44. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  45. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  46. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  47. 2026-09-21 20:32 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  48. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  49. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  50. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  51. 2026-09-17 17:06 UTCOSV refresh
  52. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  53. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  54. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  55. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  56. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  57. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  58. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  59. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  60. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  61. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  62. 2026-09-04 13:59 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  63. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  64. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  65. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  66. 2026-09-01 04:37 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  67. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  68. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  69. 2026-08-29 17:13 UTCOSV refresh
  70. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  71. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.4% · 69th percentile

Frequently asked(5)

What is CVE-2024-37890?
CVE-2024-37890 is a high-severity vulnerability; its CVE record was published on June 17, 2024. ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and…
When was the CVE record for CVE-2024-37890 published?
The CVE record for CVE-2024-37890 was published on June 17, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-37890 actively exploited?
CVE-2024-37890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37890?
CVE-2024-37890 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-37890?
A fix for CVE-2024-37890 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-37890 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-37890

Explore →

Is Your Infrastructure Affected by CVE-2024-37890?

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