Evmos vulnerable to exploit of smart contract account and vesting (CVE-2024-39696) | HOL Guard CVE

High · CVSS 8.8CVE-2024-39696GHSA-Q6HG-6M9X-5G9C

Evmos vulnerable to exploit of smart contract account and vesting

Answer in brief

CVE-2024-39696 records a High severity (CVSS 8.8) vulnerability in Evmos vulnerable to exploit of smart contract account and vesting. The current sources do not mark it as known exploited. The current feed maps github.com/evmos/evmos/v18 (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 10, 2024Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/evmos/evmos/v18 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/evmos/evmos/v18go	>=0 <19.0.0	19.0.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/evmos/evmos/v18.
Review the reported fix. Update github.com/evmos/evmos/v18 to 19.0.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 10, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Summary This advisory board aims to describe two vulnerabilities found in the Evmos codebase: - _Authorization check on the fundVestingAccount_: unauthorized spend of funds. ### Details #### Authorization check on the fundVestingAccount With the current implementation, 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. ### Severity Based on [ImmuneFi Severity Classification System](https://immunefisupport.zendesk.com/hc/en-us/articles/13332717597585-Severity-Classification-System) the severity was evaluated to Critical since the attack could have lead to direct loss of funds. ### Patches The issue has been patched in versions >=V19.0.0

Quoted source text, attributed separately from HOL analysis.