NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

CVE-2024-32873 — evmos

LOWFix: evmos/evmos@b2a09ca

CVE-2024-32873 is a low-severity (CVSS 3.5) CWE-682 vulnerability in github.com/evmos/evmos/v17. A fix is available for github.com/evmos/evmos/v17 — see the affected versions and patch details below.

evmos allows transferring unvested tokens after delegations

Also known asCVE-2024-37158CVE-2024-37159GHSA-pxv8-qhrh-jc7vGO-2024-2891GO-2024-2926GO-2024-2927
Published
Updated
Affected
12 pkgs
Patched
12 / 12
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-32873.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk
0.00%0.29%0.59%0.88%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

12 pkgs affected
🐹github.com/evmos/evmos/v17🐹github.com/evmos/evmos/v16🐹github.com/evmos/evmos/v15🐹github.com/evmos/evmos/v14🐹github.com/evmos/evmos/v13🐹github.com/evmos/evmos/v12🐹github.com/evmos/evmos/v11🐹github.com/evmos/evmos/v10+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 15M vesting schedule. The initial spendable balance is 0.
  • Time passes and 5M are vested. The spendable balance is now 5M.
  • The account delegate 5M. The spendable balance should be 0, but returns 5M
  • The account can send 5M to 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 TrackDelegation function.
  • The checks for the staking module, for the delegation and the create validator, has been moved into the MsgServer of a wrapper around the Cosmos SDK staking module.

The issues have been patched in versions >=V18.0.0.

References

  1. Evmos vesting module

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

Affected Packages

12 total 12 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/evmos/evmos/v17all versions18.0.0go get github.com/evmos/evmos/v17@v18.0.0
🐹Gogithub.com/evmos/evmos/v16all versions18.0.0go get github.com/evmos/evmos/v16@v18.0.0
🐹Gogithub.com/evmos/evmos/v15all versions18.0.0go get github.com/evmos/evmos/v15@v18.0.0
🐹Gogithub.com/evmos/evmos/v14all versions18.0.0go get github.com/evmos/evmos/v14@v18.0.0
🐹Gogithub.com/evmos/evmos/v13all versions18.0.0go get github.com/evmos/evmos/v13@v18.0.0
🐹Gogithub.com/evmos/evmos/v12all versions18.0.0go get github.com/evmos/evmos/v12@v18.0.0

Affected Products

1 product · 1 configurations
Application
evmosevmos
< 18.0.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/evmos/evmos/v17, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/evmos/evmos/v17 to 18.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32873 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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 `15M` vesting schedule. The initial spendable balance is `0`. - Time passes and `5M` are vested. The spendable balance is now `5M`. - The account delegate `5M`. The spendable balance should be `0`, but returns `5M` - The account can se
O3 Security · Impact-Aware SCA

Is CVE-2024-32873 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2024-32873: evmos — Fixed in 18.0.0