Summary
Evmos vulnerable to unauthorized account creation with vesting module
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
References
Are there any links users can visit to find out more?
Impact
What kind of vulnerability is it? Who is impacted?
Using the vesting module, a malicious attacker can create a new vesting account at a given
address, before a contract is created on that address.
Addresses of smart contracts deployed to the EVM are deterministic. Therefore, it would be possible for an attacker to front-run a contract creation and create a vesting account at that address.
When an address has been initialized without any contract code deployed to it, it will not be possible to upload any afterwards. In the described attack, this would mean that a malicious actor could prevent smart contracts from being deployed correctly.
In order to remediate this, an alternative user flow is being implemented for the vesting module:
- only the account receiving the vesting funds will be able to create such an account by calling the
CreateClawbackVestingAccountmethod and defining a funder address - vesting and lockup periods can then be created by that funder address using
FundClawbackAccount
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
Frequently Asked Questions
- What is GHSA-M99C-Q26R-M7M7? GHSA-M99C-Q26R-M7M7 is a medium-severity security vulnerability in github.com/evmos/evmos/v13/x/vesting (go), affecting versions <= 13.0.2. No fixed version is listed yet.
- Which packages are affected by GHSA-M99C-Q26R-M7M7?
github.com/evmos/evmos/v13/x/vesting(go) (versions <= 13.0.2)github.com/evmos/evmos/v13(go) (versions <= 13.0.2)
- Is there a fix for GHSA-M99C-Q26R-M7M7? No fixed version is listed for GHSA-M99C-Q26R-M7M7 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-M99C-Q26R-M7M7 exploitable, and should I be worried? Whether GHSA-M99C-Q26R-M7M7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-M99C-Q26R-M7M7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.