CVE-2021-25835 json
Authentication bypass by capture-replay in github.com/cosmos/ethermint
published 2021-02-08 5 y ago modified 2026-06-17 4 mo ago also GHSA-x5f3-qmwj-4f84 , GO-2022-0889 , EUVD-2022-1247
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Cosmos Network Ethermint <= v0.4.0 is affected by a cross-chain transaction replay vulnerability in the EVM module. Since ethermint uses the same chainIDEpoch and signature schemes with ethereum for compatibility, a verified signature in ethereum is still valid in ethermint with the same msg content and chainIDEpoch, which enables "cross-chain transaction replay" attack.
Patch / fix
- go github.com/cosmos/ethermint 0.4.1
- github.com/cosmos/ethermint#692 pull request
- github.com/cosmos/ethermint/releases/tag/v0.4.1 release
Exploit prediction
1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cosmos/ethermint | <0.4.1 |
0.4.1 |
Classification
References
-
github.com
/cosmos/ethermint/pull/692
web, patch, third-party-advisory
-
github.com
/cosmos/ethermint/issues/687
web, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2021-25835
advisory
-
github.com
/cosmos/ethermint/releases/tag/v0.4.1
web
-
github.com
/advisories/GHSA-x5f3-qmwj-4f84
advisory
Sources
- CVE List CVE-2021-25835
- GitHub Advisory GHSA-x5f3-qmwj-4f84
- NVD CVE-2021-25835
- OSV GO-2022-0889
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.