fix(security): bump evm to GHSA Aug-2026 patched commit (testnet/v37) - #4638
Merged
Conversation
…et/v37) Points the evm dependency at the patched release/v37 tip (github.com/zeta-chain/evm @ a69d910e, zeta-chain/evm#37). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
morde08
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Testnet (node
release/zetacore/v37) node-side. One line: bumpscosmos/evmto the patched v37 commit.a69d910eis the current tip ofzeta-chain/evm'srelease/v37— the fork line testnet's v37 pins — after zeta-chain/evm#37 merged. Same guard set as mainnet.Validate on testnet first, then promote mainnet.
Note on the pin
Pinned to the merged
release/v37tip, not a PR-branch commit: #37 was squash-merged, so the pre-merge commits are unreachable and such a pin would break once the branch is deleted.The
v0.0.0-prefix matches the existing convention in thisreplaceblock;go mod tidywould canonicalise it tov1.0.0-rc2.0.20260903155126-a69d910e9214. Both name the same commit but hash differently ingo.sum.Verification
go build ./cmd/zetacoredis green and produces a working binary. NoGOPRIVATEneeded — the evm dependency is public.Note
Medium Risk
Upgrades the forked EVM stack used for ante, VM, and feemarket paths; security-critical but scoped to a known patched commit with no local logic changes.
Overview
Updates the
github.com/cosmos/evm→github.com/zeta-chain/evmreplacepin ingo.modfrom commit515bbca4d348toa69d910e9214(currentrelease/v37tip after the security backport), with matchinggo.sumentries.This is a dependency-only change for the testnet
release/zetacore/v37line: node code is unchanged, but builds now pull the GHSA Aug-2026–patched EVM fork instead of the previous pin.Reviewed by Cursor Bugbot for commit 6eefd38. Configure here.
Greptile Summary
This PR updates the testnet v37
github.com/cosmos/evmreplacement to the patchedzeta-chain/evmrelease commit.go.mod.go.sum.Confidence Score: 5/5
The PR appears safe to merge, with the replacement version and integrity hashes updated consistently and no actionable defect identified.
The change is limited to an EVM fork revision and its matching checksums; available repository evidence does not establish a build, runtime, dependency-resolution, or newly introduced security failure.
Important Files Changed
Reviews (1): Last reviewed commit: "fix(security): bump cosmos/evm to GHSA A..." | Re-trigger Greptile