How severe is GHSA-8pfh-j44r-f654?

No CVSS score has been assigned to GHSA-8pfh-j44r-f654 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8pfh-j44r-f654?

GHSA-8pfh-j44r-f654 affects the following packages: github.com/cosmos/evm (Go), github.com/cosmos/evm (Go). Ecosystems affected: Go.

How do I fix GHSA-8pfh-j44r-f654?

Update github.com/cosmos/evm to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8pfh-j44r-f654 is resolved across your whole dependency graph.

How do I detect GHSA-8pfh-j44r-f654 in my Go dependencies?

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

How do I mitigate GHSA-8pfh-j44r-f654 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-8pfh-j44r-f654 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8pfh-j44r-f654 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.

When was GHSA-8pfh-j44r-f654 published, and has it been updated?

GHSA-8pfh-j44r-f654 was published on October 21, 2025 and was last updated on November 5, 2025. 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

Cosmos EVM VulnerabilityGHSA-8pfh-j44r-f654

Fix: cosmos/evm@79089fe

GHSA-8pfh-j44r-f654 is a security vulnerability in github.com/cosmos/evm. A fix is available for github.com/cosmos/evm — see the affected versions and patch details below.

Also known asGO-2025-4041

Published

Oct 21, 2025

Updated

Nov 5, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/cosmos/evm🐹github.com/cosmos/evm

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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/evm`	≥ 0.3.0&&< 0.3.2	0.3.2`go get github.com/cosmos/evm@v0.3.2`
🐹Go	`github.com/cosmos/evm`	≥ 0.4.0&&< 0.4.2	0.4.2`go get github.com/cosmos/evm@v0.4.2`

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/cosmos/evm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cosmos/evm to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8pfh-j44r-f654 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

## 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.

O3 Security · Impact-Aware SCA

Is GHSA-8pfh-j44r-f654 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works