Account compromise in Evmos

Exploitation

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

CVSS

7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2022-24738: 1.07% estimated exploitation activity in the next 30 days; percentile 64.85 (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? Classification The vulnerability has been classified as critical with a score of 9.0 (highest). It has the potential to affect and drain unclaimed airdrop funds from Cosmos and Osmosis eligible user addresses. Disclosure The attack requires advanced knowledge of the internals of the core and application packages of IBC, IBC relayers, the Cosmos SDK AnteHandler, and the Evmos x/claims module. The step-by-step attack is described below: 1. An actor creates a malicious chain with a custom AnteHandler that skips signature verification for transactions, specifically IBC MsgTransfer. This allows the attacker to impersonate any account by setting a custom sender address field of the IBC transfer message. 2. The malicious actor then connects this newly created chain via IBC to Evmos and fills the recipient address from the transfer message with an address they control. 3. Once the IBC packet containing the Transfer data is relayed to…

Published by the source

7 Mar 2022, 21:45 UTC

Last modified by the source

16 Jan 2024, 13:44 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5jgq-x857-p8xw

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

# Patch Next advisory brief: CVE-2022-24738

Advisory: Account compromise in Evmos
IDs: CVE-2022-24738, GHSA-5jgq-x857-p8xw
Record: https://patchnext.com/advisories/cve-2022-24738 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tharsis/evmos 2.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tharsis/evmos: affected < 2.0.1; fixed in 2.0.1

## Suggested inspection (read-only)
- Go github.com/tharsis/evmos: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tharsis/evmos.
- 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-5jgq-x857-p8xw (GitHub-reviewed advisory GHSA-5jgq-x857-p8xw lists affected ranges: Go github.com/tharsis/evmos >=0 <2.0.1)

Commands are suggestions: review each one before running it.