CVE-2024-48930

HIGHNVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-2944 (ENISA EUVD) · GHSA-584q-6j8j-r5pm (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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: 0.4%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

secp256k1-node is a Node.js binding for an Optimized C library for EC operations on curve secp256k1. In elliptic-based version, loadUncompressedPublicKey has a check that the public key is on the curve. Prior to versions 5.0.1, 4.0.4, and 3.8.1, however, loadCompressedPublicKey is missing that check. That allows the attacker to use public keys on low-cardinality curves to extract enough information to fully restore the private key from as little as 11 ECDH sessions, and very cheaply on compute power. Other operations on public keys are also affected, including e.g. publicKeyVerify() incorrectly returning true on those invalid keys, and e.g. publicKeyTweakMul() also returning predictable outcomes allowing to restore the tweak. Versions 5.0.1, 4.0.4, and 3.8.1 contain a fix for the issue.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 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
0.4%
EPSS %ILE
34th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

October 21, 2024

Last Modified

April 15, 2026

Advisory Details (6)

Auto-updated Sep 1, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Private key extraction over ECDH · Advisory · cryptocoinjs/secp256k1-node · GitHub

https://github.com/cryptocoinjs/secp256k1-node/security/advisories/GHSA-584q-6j8j-r5pm
GitHub commit

commit e256905ee649 (cryptocoinjs/secp256k1-node)

Fix landed in cryptocoinjs/secp256k1-node commit e256905ee649 — awaiting tagged release

https://github.com/cryptocoinjs/secp256k1-node/commit/e256905ee649a7caacc251f7c964667195a52221
GitHub commit

commit 9a15fff274f8 (cryptocoinjs/secp256k1-node)

Fix landed in cryptocoinjs/secp256k1-node commit 9a15fff274f8 — awaiting tagged release

https://github.com/cryptocoinjs/secp256k1-node/commit/9a15fff274f83a6ec7f675f1121babcc0c42292f
GitHub commit

commit 8bd6446e000f (cryptocoinjs/secp256k1-node)

Fix landed in cryptocoinjs/secp256k1-node commit 8bd6446e000f — awaiting tagged release

https://github.com/cryptocoinjs/secp256k1-node/commit/8bd6446e000fa59df3cda0ae3e424300747ea5ed
Web page

secp256k1-node/lib/elliptic.js at 6d3474b81d073cc9c8cc8cfadb580c84f8df5248 · cryptocoinjs/secp256k1-node · GitHub

https://github.com/cryptocoinjs/secp256k1-node/blob/6d3474b81d073cc9c8cc8cfadb580c84f8df5248/lib/elliptic.js#L37-L39
Web page

secp256k1-node/lib/elliptic.js at 6d3474b81d073cc9c8cc8cfadb580c84f8df5248 · cryptocoinjs/secp256k1-node · GitHub

https://github.com/cryptocoinjs/secp256k1-node/blob/6d3474b81d073cc9c8cc8cfadb580c84f8df5248/lib/elliptic.js#L17-L19

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsecp256k1 @ 5.0.1 (fixes = 5.0.0)—ghsa
npmsecp256k1 @ 4.0.4 (fixes >= 4.0.0, < 4.0.4)—ghsa
npmsecp256k1 @ 3.8.1 (fixes <= 3.8.0)—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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
secp256k15.0.0
  • 5.0.0 up to 5.0.1: fixed in 5.0.1
  • 4.0.0 up to 4.0.4: fixed in 4.0.4
  • every version up to 3.8.1: fixed in 3.8.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 94 of 233 refreshes on record for this CVE.

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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-584q-6j8j-r5pm · GitHub severity HIGH
  4. 2026-11-01 08:11 UTCEG score recompute
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-27 18:11 UTCEG score recompute
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-25 17:00 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-19 19:21 UTCEG score recompute
  20. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-18 06:56 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 69 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-12 17:42 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-11 21:08 UTCEG score recompute
  6. 2026-10-11 16:00 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-10 23:17 UTCOSV refresh
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-30 19:55 UTCEG score recompute
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-09-21 11:19 UTCOSV refresh
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-09-02 09:34 UTCOSV refresh
  47. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  49. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  59. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  63. 2026-08-16 08:17 UTCOSV refresh
  64. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  66. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  67. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  68. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  69. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2024-48930?
CVE-2024-48930 is a high-severity vulnerability; its CVE record was published on October 21, 2024. secp256k1-node is a Node.js binding for an Optimized C library for EC operations on curve secp256k1. In elliptic-based version, loadUncompressedPublicKey has a check that the public key is on the curve. Prior to versions 5.0.1, 4.0.4, and 3.8.1, however, loadCompressedPublicKey is missing that…
When was the CVE record for CVE-2024-48930 published?
The CVE record for CVE-2024-48930 was published on October 21, 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-48930 actively exploited?
CVE-2024-48930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-48930?
CVE-2024-48930 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2024-48930?
A fix for CVE-2024-48930 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-48930?

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