CVE-2024-32873
evmos allows transferring unvested tokens after delegations
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Required
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
3.5
evmos allows transferring unvested tokens after delegations
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.
- Record
CVE-2024-32873- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-682
- Updated
- 2026-11-02
EUVDEUVD-2024-2129
3.5
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.
- Record
EUVD-2024-2129- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-pxv8-qhrh-jc7v
3.5
evmos allows transferring unvested tokens after delegations
Impact
This advisory has been created to address the following vulnerabilities found in the Evmos codebase and affecting vesting accounts.
Wrong spendable balance computation
The spendable balance is not updated properly when delegating vested tokens. The following example help in describing the issue:
- Given a clawback vesting account with a starting
15Mvesting schedule. The initial spendable balance is0. - Time passes and
5Mare vested. The spendable balance is now5M. - The account delegate
5M. The spendable balance should be0, but returns5M - The account can send
5Mto another account.
The issue allowed a clawback vesting account to anticipate the release of unvested tokens.
Missing precompile checks
Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different.
The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module.
Missing create validator check
This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond.
Patches
- The spendable balance function has been fixed correcting the
TrackDelegationfunction. - The checks for the staking module, for the delegation and the create validator, has been moved into the
MsgServerof a wrapper around the Cosmos SDK staking module.
The issues have been patched in versions >=V18.0.0.
References
For more information
If you have any questions or comments about this advisory:
Reach out to the Core Team in Discord Open a discussion in evmos/evmos Email us at [email protected] for security questions
- Record
GHSA-pxv8-qhrh-jc7v- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-682
- Updated
- 2026-11-02
NVD
3.5
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.
- Record
CVE-2024-32873- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-682
- Updated
- 2026-11-02
OSV
3.5
evmos allows transferring unvested tokens after delegations
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.
- Record
CVE-2024-32873- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-682
- Updated
- 2026-11-02
OSVCVE-2024-37158
3.5
Evmos is missing precompile checks
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. This vulnerability is fixed in 18.0.0.
- Record
CVE-2024-37158- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-691
- Updated
- 2026-11-02
Show 5 moreShow less
OSVCVE-2024-37159
3.5
Evmos is missing create validator check
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. This vulnerability is fixed in 18.0.0.
- Record
CVE-2024-37159- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-285
- Updated
- 2026-11-02
OSVGHSA-pxv8-qhrh-jc7v
3.5
evmos allows transferring unvested tokens after delegations
Impact
This advisory has been created to address the following vulnerabilities found in the Evmos codebase and affecting vesting accounts.
Wrong spendable balance computation
The spendable balance is not updated properly when delegating vested tokens. The following example help in describing the issue:
- Given a clawback vesting account with a starting
15Mvesting schedule. The initial spendable balance is0. - Time passes and
5Mare vested. The spendable balance is now5M. - The account delegate
5M. The spendable balance should be0, but returns5M - The account can send
5Mto another account.
The issue allowed a clawback vesting account to anticipate the release of unvested tokens.
Missing precompile checks
Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different.
The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module.
Missing create validator check
This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond.
Patches
- The spendable balance function has been fixed correcting the
TrackDelegationfunction. - The checks for the staking module, for the delegation and the create validator, has been moved into the
MsgServerof a wrapper around the Cosmos SDK staking module.
The issues have been patched in versions >=V18.0.0.
References
For more information
If you have any questions or comments about this advisory:
Reach out to the Core Team in Discord Open a discussion in evmos/evmos Email us at [email protected] for security questions
- Record
GHSA-pxv8-qhrh-jc7v- CVSS 3.1
- 3.5 Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-682
- Updated
- 2026-11-02
OSVGO-2024-2891 No score
evmos allows transferring unvested tokens after delegations in github.com/evmos/evmos
evmos allows transferring unvested tokens after delegations in github.com/evmos/evmos
- Record
GO-2024-2891- Updated
- 2026-11-02
OSVGO-2024-2926 No score
Evmos is missing precompile checks in github.com/evmos/evmos
Evmos is missing precompile checks in github.com/evmos/evmos
- Record
GO-2024-2926- Updated
- 2026-11-02
OSVGO-2024-2927 No score
Evmos is missing create validator check in github.com/evmos/evmos
Evmos is missing create validator check in github.com/evmos/evmos
- Record
GO-2024-2927- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/evmos/evmos/v17Go |
through 17.0.1 | 18.0.0 |
github.com/evmos/evmos/v16Go |
through 16.0.4 | 18.0.0 |
github.com/evmos/evmos/v15Go |
through 15.0.0 | 18.0.0 |
github.com/evmos/evmos/v14Go |
through 14.1.0 | 18.0.0 |
github.com/evmos/evmos/v13Go |
through 13.0.2 | 18.0.0 |
github.com/evmos/evmos/v12Go |
through 12.1.6 | 18.0.0 |
github.com/evmos/evmos/v11Go |
through 11.0.2 | 18.0.0 |
github.com/evmos/evmos/v10Go |
through 10.0.1 | 18.0.0 |
github.com/evmos/evmos/v9Go |
through 9.1.0 | 18.0.0 |
github.com/evmos/evmos/v8Go |
through 8.2.3 | 18.0.0 |
Show 32 moreShow less
| Package | Affected | Fixed |
|---|---|---|
github.com/evmos/evmos/v7Go |
through 7.0.0 | 18.0.0 |
github.com/evmos/evmos/v6Go |
through 6.0.4 | 18.0.0 |
github.com/evmos/evmos/v17Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v16Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v15Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v14Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v13Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v12Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v11Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v10Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v9Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v8Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v7Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmos/v6Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
github.com/evmos/evmosGo From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v2Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v3Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v4Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v5Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v6Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v7Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v8Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v9Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v10Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v11Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v12Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v13Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v14Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v15Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v16Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v17Go From an advisory covering 3 CVEs |
All versions | None known |
github.com/evmos/evmos/v18Go From an advisory covering 3 CVEs |
before 18.0.0 | 18.0.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases, products, published | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-32873 is a low vulnerability (CVSS 3.5) in Evmos, published June 6, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.38%, the 32nd percentile. Fixed in github.com/evmos/evmos/v17 18.0.0.
References
github.com/evmos/evmos/security/advisories/GHSA-pxv8-qhrh-jc7v
github.com/evmos/evmos/commit/b2a09ca66613d8b04decd3f2dcba8e1e77709dcb
nvd.nist.gov/vuln/detail/CVE-2024-32873
pkg.go.dev/vuln/GO-2024-2891
nvd.nist.gov/vuln/detail/CVE-2024-37158
nvd.nist.gov/vuln/detail/CVE-2024-37159