How severe is GHSA-f854-hpxv-cw9r?

GHSA-f854-hpxv-cw9r has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-f854-hpxv-cw9r?

GHSA-f854-hpxv-cw9r affects the following packages: github.com/crypto-org-chain/cronos (Go), github.com/tharsis/ethermint (Go), github.com/tharsis/evmos (Go), github.com/tharsis/ethermint (Go). Ecosystems affected: Go.

How do I fix GHSA-f854-hpxv-cw9r?

Update github.com/crypto-org-chain/cronos to 0.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f854-hpxv-cw9r is resolved across your whole dependency graph.

How do I detect GHSA-f854-hpxv-cw9r in my Go dependencies?

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

How do I mitigate GHSA-f854-hpxv-cw9r if there is no patch (or I can't update yet)?

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.

Is GHSA-f854-hpxv-cw9r actively exploited in the wild?

No public exploit code has been indexed for GHSA-f854-hpxv-cw9r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-f854-hpxv-cw9r?

GHSA-f854-hpxv-cw9r has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-f854-hpxv-cw9r?

GHSA-f854-hpxv-cw9r is classified as CWE-670 (CWE-670). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f854-hpxv-cw9r published, and has it been updated?

GHSA-f854-hpxv-cw9r was published on January 6, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

Drainage of FeeCollector's Block Transaction Fees in cronosGHSA-f854-hpxv-cw9r

HIGHFix: crypto-org-chain/cronos#270

GHSA-f854-hpxv-cw9r is a high-severity (CVSS 7.5) CWE-670 vulnerability in github.com/crypto-org-chain/cronos. A fix is available for github.com/crypto-org-chain/cronos — see the affected versions and patch details below.

Also known asCVE-2021-43839

Published

Jan 6, 2022

Updated

Jul 8, 2026

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-f854-hpxv-cw9r by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

🐹github.com/crypto-org-chain/cronos🐹github.com/tharsis/ethermint🐹github.com/tharsis/evmos🐹github.com/tharsis/ethermint

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

In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx.

User funds and balances are safe.

Patches

This problem has been patched in Cronos v0.6.5 on the mempool level. The next network upgrade with consensus-breaking changes will patch it on the consensus level.

Workarounds

There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience.

Credits

Thank you to @zb3 for reporting this issue on Cronos Immunefi Bug Bounty Program, to @cyril-crypto for reproducing the issue and to @yihuang and @thomas-nguy for patching the issue on the CheckTx (mempool) and the DeliverTx (consensus) levels.

For more information

If you have any questions or comments about this advisory:

Open a discussion in crypto-org-chain/cronos
Email us at [email protected]

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/crypto-org-chain/cronos`	all versions	0.6.5`go get github.com/crypto-org-chain/cronos@v0.6.5`
🐹Go	`github.com/tharsis/ethermint`	≥ 0.8.0&&< 0.10.0	0.10.0`go get github.com/tharsis/ethermint@v0.10.0`
🐹Go	`github.com/tharsis/evmos`	all versions	No fix
🐹Go	`github.com/tharsis/ethermint`	all versions	0.7.3`go get github.com/tharsis/ethermint@v0.7.3`

Affected Products

3 products · 4 configurations

Application

cronoscrypto

< 0.6.5

range

Application

ethermintcrypto

≥ 0.8.0 && ≤ 0.9.0

range

Application

evmoscrypto

≤ 0.4.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crypto-org-chain/cronos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/crypto-org-chain/cronos to 0.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f854-hpxv-cw9r is resolved across your whole dependency graph.
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 In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx. User funds and balances are safe. ### Patches This problem has been patched in Cronos v0.6.5 on the mempool level. The next network upgrade with consensus-breaking changes will patch it on the consensus level. ### Workarounds There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience. ### Credits Thank you to @zb