Denial of service in geth
Published 29 Jun 2021 · Updated 8 Jul 2026
Is your project on an affected github.com/ethereum/go-ethereum?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=1.9.16 <1.9.18
- Fixed in
- 1.9.18
go get github.com/ethereum/go-ethereum@v1.9.18- Affected
- >=0.1.0 <1.1.1
- Fixed in
- 1.1.1
go get github.com/holiman/uint256@v1.1.1Details
Impact
Denial-of-service (crash) during block processing
Details
Affected versions suffer from a vulnerability which can be exploited through the MULMOD operation, by specifying a modulo of 0: mulmod(a,b,0), causing a panic in the underlying library.
The crash was in the uint256 library, where a buffer underflowed.
if d == 0, dLen remains 0
and https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index [-1].
The uint256 library was first merged in this commit, on 2020-06-08.
Exploiting this vulnerabilty would cause all vulnerable nodes to drop off the network.
The issue was brought to our attention through a bug report, showing a panic occurring on sync from genesis on the Ropsten network.
It was estimated that the least obvious way to fix this would be to merge the fix into uint256, make a new release of that library and then update the geth-dependency.
- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day,
- PR to address the issue: https://github.com/holiman/uint256/pull/80
- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368
Patches
Upgrade to v1.9.18 or higher
Workarounds
Not at this time
References
https://blog.ethereum.org/2020/11/12/geth_security_release/
For more information
If you have any questions or comments about this advisory:
- Open an issue in go-ethereum
- Email us at [security@ethereum.org](mailto:security@ethereum.org)
Is GHSA-jm5c-rv3w-w83m in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/ethereum/go-ethereum, and gives you the command that fixes it.
More advisories for github.com/ethereum/go-ethereum
- LowCVE-2026-26314Go Ethereum affected by crash via malicious p2p message in github.com/ethereum/go-ethereum · 24 Feb 2026
- LowCVE-2026-26313Go Ethereum affected by DoS via malicious p2p message in github.com/ethereum/go-ethereum · 24 Feb 2026
- LowCVE-2026-26315Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake in github.com/ethereum/go-ethereum · 24 Feb 2026
- MediumCVE-2026-26315Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake · 18 Feb 2026
- HighCVE-2026-26314Go Ethereum affected by DoS via malicious p2p message · 18 Feb 2026
- MediumCVE-2026-26313Go Ethereum affected by DoS via malicious p2p message · 18 Feb 2026
References
- Linkgithub.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m
- Advisorynvd.nist.gov/vuln/detail/CVE-2020-26242
- Linkgithub.com/holiman/uint256/pull/80
- Linkgithub.com/ethereum/go-ethereum/commit/7163a6664ee664df81b9028ab3ba13b9d65a7196
- Linkgithub.com/holiman/uint256/commit/6785da6e3eea403260a5760029e722aa4ff1716d
- Linkblog.ethereum.org/2020/11/12/geth_security_release
- Packagegithub.com/ethereum/go-ethereum
- Linkpkg.go.dev/vuln/GO-2021-0103
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.