Summary
Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake
Credit
The issue was reported as a public pull request to go-ethereum by @fengjian.
Impact
Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-26315? CVE-2026-26315 is a medium-severity security vulnerability in github.com/ethereum/go-ethereum (go), affecting versions <= 1.16.8. It is fixed in 1.16.9.
- Which versions of github.com/ethereum/go-ethereum are affected by CVE-2026-26315? github.com/ethereum/go-ethereum (go) versions <= 1.16.8 is affected.
- Is there a fix for CVE-2026-26315? Yes. CVE-2026-26315 is fixed in 1.16.9. Upgrade to this version or later.
- Is CVE-2026-26315 exploitable, and should I be worried? Whether CVE-2026-26315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-26315 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-26315? Upgrade
github.com/ethereum/go-ethereumto 1.16.9 or later.