Skip to content
Fencer Intel
critical —

GHSA-8pfh-j44r-f654 json

Cosmos EVM Vulnerability

published last yr. modified 8mo ago also GO-2025-4041

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Patches Patched in versions `v0.3.1`, `v0.4.2`, and in the `v0.5.0` release. More information will be disclosed at a later point to ensure chains have time to safely upgrade.

## Workarounds No workarounds for chains that make use of static or dynamic precompiles. Upgrading is strongly recommended.

## Testing Tests are introduced in every affected version.

## Credits Special thanks to @yihuang for the help on this issue.

Patch / fix

  • go github.com/cosmos/evm 0.3.2, 0.4.2

Is GHSA-8pfh-j44r-f654 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/cosmos/evm
>=0.3.0, <0.3.2
>=0.4.0, <0.4.2
0.3.2
0.4.2

References

Sources

Fencer Intel 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.