CVE-2026-26315 Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake

Medium 6.9 Published Updated

An attacker can extract bits of the P2P node key due to improper ECIES public key validation, potentially compromising node identity and security.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-26315?

CVE-2026-26315 is a medium-severity vulnerability in go-ethereum, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

go-ethereum (Geth) is a golang execution layer implementation of the Ethereum protocol. Prior to version 1.16.9, through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key. The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. Geth maintainers recommend rotating the node key after applying the upgrade, which can be done by removing the file `<datadir>/geth/nodekey` before starting Geth.

Weakness: CWE-203

Which versions are affected by CVE-2026-26315?

3 open source packages ship an affected version, including github.com/ethereum/go-ethereum. It affects 1 product.

PackageAffectedFixed in
github.com/ethereum/go-ethereum GoAll versions1.16.9
github.com/ethereum/go-ethereum GoAll versions1.16.9
github.com/ethereum/go-ethereum GoAll versions1.16.9

Products include Ethereum Go Ethereum.

How do I fix CVE-2026-26315?

Upgrade github.com/ethereum/go-ethereum to 1.16.9 or later.

Is CVE-2026-26315 being exploited?

There is no known exploitation of CVE-2026-26315 in the wild and no public exploit code.

Sources

Also known as GHSA-m6j8-rg6r-7mv8, GO-2026-4511.

Is CVE-2026-26315 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free