Evmos is a decentralized Ethereum Virtual Machine chain on the Cosmos Network. Prior to version 19.0.0, a user can create a vesting account with a 3rd party account (EOA or contract) as funder. Then, this user can create an authorization for the contract.CallerAddress, this is the authorization checked in the code. But the funds are taken from the funder address provided in the message. Consequently, the user can fund a vesting account with a 3rd party account without its permission. The funder address can be any address, so this vulnerability can be used to drain all the accounts in the chain. The issue has been patched in version 19.0.0.
CVE-2024-39696
HIGHNVD 8.88.8Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-07-10. NVD baseline CVSS 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Also known asEUVD-2024-2400 (ENISA EUVD) · GHSA-q6hg-6m9x-5g9c (GitHub Security Advisories)Source: ENISA EUVD
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 40EG Risk 40/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)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (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. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- 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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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
July 5, 2024
Last Modified
March 7, 2025
Advisory Details (2)
Auto-updated Aug 1, 2026Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)
Precompiles exploit of smart contract account and vesting · Advisory · evmos/evmos · GitHub
Affected: versions >=V19.0.0
https://github.com/evmos/evmos/security/advisories/GHSA-q6hg-6m9x-5g9cGitHub commit
commit 0a620e176617 (evmos/evmos)
Fix landed in evmos/evmos commit 0a620e176617 — awaiting tagged release
https://github.com/evmos/evmos/commit/0a620e176617a835ac697eea494afea09185dfafPatch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/evmos/evmos/v18 @ 19.0.0 (fixes <= 18.0.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
(19 across 1 ecosystem)
Go(19)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/evmos/evmos | — |
| — |
| github.com/evmos/evmos/v10 | — |
| — |
| github.com/evmos/evmos/v11 | — |
| — |
| github.com/evmos/evmos/v12 | — |
| — |
| github.com/evmos/evmos/v13 | — |
| — |
| github.com/evmos/evmos/v14 | — |
| — |
| github.com/evmos/evmos/v15 | — |
| — |
| github.com/evmos/evmos/v16 | — |
| — |
| github.com/evmos/evmos/v17 | — |
| — |
| github.com/evmos/evmos/v18 | — |
| — |
| github.com/evmos/evmos/v19 | — |
| — |
| github.com/evmos/evmos/v2 | — |
| — |
| github.com/evmos/evmos/v3 | — |
| — |
| github.com/evmos/evmos/v4 | — |
| — |
| github.com/evmos/evmos/v5 | — |
| — |
| github.com/evmos/evmos/v6 | — |
| — |
| github.com/evmos/evmos/v7 | — |
| — |
| github.com/evmos/evmos/v8 | — |
| — |
| github.com/evmos/evmos/v9 | — |
| — |
Weakness Classification(1)
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 96 of 217 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 08:13 UTCGHSA enrichmentGHSA-q6hg-6m9x-5g9c · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-01 08:13 UTCEG score recompute
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 15:12 UTCEG score recompute
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 17:06 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-20 19:36 UTCEG score recompute
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 07:09 UTCEG score recompute
- 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 71 moreShow fewer
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-12 17:49 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-11 21:14 UTCEG score recompute
- 2026-10-11 16:07 UTCEG score recompute
- 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-10 14:33 UTCOSV refresh
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-30 19:49 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-21 00:06 UTCOSV refresh
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-01 23:31 UTCOSV refresh
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-16 01:37 UTCOSV refresh
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Related CVEs(same product + same CWE)
Same product
7 shownGo:github.com/evmos/evmos/v18 · Go:github.com/evmos/evmos/v10 · Go:github.com/evmos/evmos
Frequently asked(5)
What is CVE-2024-39696?
CVE-2024-39696 is a high-severity vulnerability; its CVE record was published on July 5, 2024. Evmos is a decentralized Ethereum Virtual Machine chain on the Cosmos Network. Prior to version 19.0.0, a user can create a vesting account with a 3rd party account (EOA or contract) as funder. Then, this user can create an authorization for the contract.CallerAddress, this is the authorization…
When was the CVE record for CVE-2024-39696 published?
The CVE record for CVE-2024-39696 was published on July 5, 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 7, 2025; the record at its source may have been updated since.
Is CVE-2024-39696 actively exploited?
CVE-2024-39696 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39696?
CVE-2024-39696 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-39696?
A fix for CVE-2024-39696 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-39696
Is Your Infrastructure Affected by CVE-2024-39696?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.