Evmos allows unvested token delegations

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2024-37154: 0.38% estimated exploitation activity in the next 30 days; percentile 32.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? At the moment, users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via ClawbackVestingAccount. Patches Has the problem been patched? What versions should users upgrade to? The PR linked to this advisory includes part of the fix. The remainder is in a second advisory on the Cosmos SDK fork. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? There is no effective workaround to fix or remediate this issue without a new release. The best solution is to contain the information about this vulnerability to minimize the number of users who know about it and can thus exploit it. References Are there any links users can visit to find out more? See the integration tests for more details on the exploit, or use the following to reproduce it on the CLI: 1. Download vestingsetup.json with the following contents: 2. Run the…

Published by the source

6 Jun 2024, 19:10 UTC

Last modified by the source

15 Oct 2024, 23:34 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7hrh-v6wp-53vw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-37154

Advisory: Evmos allows unvested token delegations
IDs: CVE-2024-37154, GHSA-7hrh-v6wp-53vw
Record: https://patchnext.com/advisories/cve-2024-37154 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/evmos/evmos/v10: affected <= 10.0.1
- Go github.com/evmos/evmos/v15: affected <= 15.0.0
- Go github.com/evmos/evmos/v6: affected <= 6.0.4
- Go github.com/evmos/evmos/v7: affected <= 7.0.0
- Go github.com/evmos/evmos/v16: affected <= 16.0.4
- Go github.com/evmos/evmos/v18: affected <= 18.1.0
- Go github.com/evmos/evmos/v13: affected <= 13.0.2
- Go github.com/evmos/evmos/v14: affected <= 14.1.0
- Go github.com/evmos/evmos/v17: affected <= 17.0.1
- Go github.com/evmos/evmos/v8: affected <= 8.2.3
- Go github.com/evmos/evmos/v12: affected <= 12.1.6
- Go github.com/evmos/evmos/v9: affected <= 9.1.0
- Go github.com/evmos/evmos/v11: affected <= 11.0.2

## Suggested inspection (read-only)
- Go github.com/evmos/evmos/v10: check the installed version with your package manager.
- Go github.com/evmos/evmos/v15: check the installed version with your package manager.
- Go github.com/evmos/evmos/v6: check the installed version with your package manager.
- Go github.com/evmos/evmos/v7: check the installed version with your package manager.
- Go github.com/evmos/evmos/v16: check the installed version with your package manager.
- Go github.com/evmos/evmos/v18: check the installed version with your package manager.
- Go github.com/evmos/evmos/v13: check the installed version with your package manager.
- Go github.com/evmos/evmos/v14: check the installed version with your package manager.
- Go github.com/evmos/evmos/v17: check the installed version with your package manager.
- Go github.com/evmos/evmos/v8: check the installed version with your package manager.
- Go github.com/evmos/evmos/v12: check the installed version with your package manager.
- Go github.com/evmos/evmos/v9: check the installed version with your package manager.
- Go github.com/evmos/evmos/v11: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/evmos/evmos/v10, github.com/evmos/evmos/v15, github.com/evmos/evmos/v6, github.com/evmos/evmos/v7, github.com/evmos/evmos/v16, github.com/evmos/evmos/v18, github.com/evmos/evmos/v13, github.com/evmos/evmos/v14, github.com/evmos/evmos/v17, github.com/evmos/evmos/v8, github.com/evmos/evmos/v12, github.com/evmos/evmos/v9, github.com/evmos/evmos/v11.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7hrh-v6wp-53vw (GitHub-reviewed advisory GHSA-7hrh-v6wp-53vw lists affected ranges: Go github.com/evmos/evmos/v18 >=0 =0 =0 =0 =0 =0 =0 =0 =0 =0…)

Commands are suggestions: review each one before running it.