CVE-2024-32644

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2024-04-10. NVD baseline CVSS 9.1; sources differ by 0.0.

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

Also known asEUVD-2024-1080 (ENISA EUVD) · GHSA-3fp5-2xwh-fxm6 (GitHub Security Advisories) · GO-2024-2715 (OSV.dev)Source: ENISA EUVD

9.1EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the stateDB.Commit() method. When we call this method, we iterate though all the dirtyStorage and, if and only if it is different than the originStorage, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is critical since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.9%
EPSS %ILE
61st
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% 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: 3 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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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

April 19, 2024

Last Modified

March 6, 2025

Advisory Details (3)

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

Transaction execution not accounting for all state transition after interaction with precompiles · Advisory · evmos/evmos · GitHub

Affected: versions >=V17.0.0.

https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
GitHub commit

commit 08982b5ee726 (evmos/evmos)

Fix landed in evmos/evmos commit 08982b5ee726 — awaiting tagged release

https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
Web page

evmos/x/evm/statedb/statedb.go at b196a522ba4951890b40992e9f97aa610f8b5f9c · evmos/evmos · GitHub

https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465

Vendor Advisories for CVE-2024-32644(1)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/evmos/evmos/v16 @ 17.0.0 (fixes <= 16.0.4)—ghsa
gogithub.com/evmos/evmos/v5—ghsa
gogithub.com/evmos/evmos/v6—ghsa
gogithub.com/evmos/evmos/v7—ghsa
gogithub.com/tharsis/evmos—ghsa
gogithub.com/tharsis/evmos/v2—ghsa
gogithub.com/tharsis/evmos/v3—ghsa
gogithub.com/tharsis/evmos/v4—ghsa
gogithub.com/tharsis/evmos/v5—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

(22 across 1 ecosystem)
Go(22)
PackageVulnerable rangeFix by version rangeDependents
github.com/evmos/evmos—
  • every version on: no fix on record
—
github.com/evmos/evmos/v10—
  • every version on: no fix on record
—
github.com/evmos/evmos/v11—
  • every version on: no fix on record
—
github.com/evmos/evmos/v12—
  • every version on: no fix on record
—
github.com/evmos/evmos/v13—
  • every version on: no fix on record
—
github.com/evmos/evmos/v14—
  • every version on: no fix on record
—
github.com/evmos/evmos/v15—
  • every version on: no fix on record
—
github.com/evmos/evmos/v16—
  • every version up to 17.0.0: fixed in 17.0.0
  • every version on: no fix on record
—
github.com/evmos/evmos/v17—
  • every version up to 17.0.0: fixed in 17.0.0
—
github.com/evmos/evmos/v2—
  • every version on: no fix on record
—
github.com/evmos/evmos/v3—
  • every version on: no fix on record
—
github.com/evmos/evmos/v4—
  • every version on: no fix on record
—
github.com/evmos/evmos/v5—
  • every version through 5.0.0: no fix on record
  • every version on: no fix on record
—
github.com/evmos/evmos/v6—
  • every version through 6.0.4: no fix on record
  • every version on: no fix on record
—
github.com/evmos/evmos/v7—
  • every version through 7.0.0: no fix on record
  • every version on: no fix on record
—
github.com/evmos/evmos/v8—
  • every version on: no fix on record
—
github.com/evmos/evmos/v9—
  • every version on: no fix on record
—
github.com/tharsis/evmos—
  • every version through 1.1.3: no fix on record
  • every version on: no fix on record
—
github.com/tharsis/evmos/v2—
  • every version through 2.0.2: no fix on record
  • every version on: no fix on record
—
github.com/tharsis/evmos/v3—
  • every version through 3.0.3: no fix on record
  • every version on: no fix on record
—
github.com/tharsis/evmos/v4—
  • every version through 4.0.2: no fix on record
  • every version on: no fix on record
—
github.com/tharsis/evmos/v5—
  • every version through 5.0.1: no fix on record
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 275 rows on record for this CVE, as 99 entries (1 repeat 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 175 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-32644?
CVE-2024-32644 is a critical-severity vulnerability; its CVE record was published on April 19, 2024. Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is…
When was the CVE record for CVE-2024-32644 published?
The CVE record for CVE-2024-32644 was published on April 19, 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 March 6, 2025; the record at its source may have been updated since.
Is CVE-2024-32644 actively exploited?
CVE-2024-32644 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32644?
CVE-2024-32644 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-32644?
A fix for CVE-2024-32644 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-32644 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-32644

Explore →

Is Your Infrastructure Affected by CVE-2024-32644?

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

Book a Demo →Browse All CVEs