MediumGHSA-xw37-57qp-9mm4CVE-2020-26265GO-2021-0105

Consensus flaw during block processing in github.com/ethereum/go-ethereum

Published 29 Jun 2021 · Updated 10 Sept 2026

Is your project on an affected github.com/ethereum/go-ethereum?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.9.4 <1.9.20
Fixed in
1.9.20
Update to the fixed version for your release line, for example:go get github.com/ethereum/go-ethereum@v1.9.20

Details

Impact

A consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain.

Description

A flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure.

  • Tx 1:
  • sender invokes caller.
  • caller invokes 0xaa. 0xaa has 3 wei, does a self-destruct-to-self
  • caller does a 1 wei -call to 0xaa, who thereby has 1 wei (the code in 0xaa still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero)
  • Tx 2:
  • sender does a 5-wei call to 0xaa. No exec (since no code).

In geth, the result would be that 0xaa had 6 wei, whereas OE reported (correctly) 5 wei. Furthermore, in geth, if the second tx was not executed, the 0xaa would be destructed, resulting in 0 wei. Thus obviously wrong.

It was determined that the root cause was this commit from this PR. The semantics of createObject was subtly changd, into returning a non-nil object (with deleted=true) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old balance:

func (s *StateDB) CreateAccount(addr common.Address) {
	newObj, prev := s.createObject(addr)
	if prev != nil {
		newObj.setBalance(prev.data.Balance)
	}
}

It was determined that the minimal possible correct fix was

+++ b/core/state/statedb.go
@@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject)
                s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct})
        }
        s.setStateObject(newobj)
-       return newobj, prev
+       if prev != nil && !prev.deleted {
+               return newobj, prev
+       }
+       return newobj, nil

Patches

See above. The fix was included in Geth v1.9.20 "Paragade".

Credits

The bug was found by @johnyangk and reported via bounty@ethereum.org.

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-xw37-57qp-9mm4 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
All 44 advisories for github.com/ethereum/go-ethereum

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.