CVE-2026-26315
Go vulnerability
### Impact Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key. ### Patches The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. We recommend rotating the node key after applying the upgrade, which can be done by removing the file `<datadir>/geth/nodekey` before starting Geth. ### Credit The issue was reported as a public pull request to go-ethereum by @fengjian.
Affected products
Go. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Go runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/ethereum/go-ethereum/security/advisories/GHSA-m6j8-rg6r-7mv8
- github.com/ethereum/go-ethereum/pull/33669
- github.com/ethereum/go-ethereum/commit/46bee92f9e64c0a06a12586a5d21cffc49d1ba8e
- github.com/ethereum/go-ethereum/releases/tag/v1.16.9
- github.com/advisories/GHSA-m6j8-rg6r-7mv8
- nvd.nist.gov/vuln/detail/CVE-2026-26315
- pkg.go.dev/vuln/GO-2026-4511
- nvd.nist.gov/vuln/detail/CVE-2026-26315
- cve.org/CVERecord?id=CVE-2026-26315
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.