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

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

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-m6j8-rg6r-7mv8, GO-2026-4511

## 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 (Observable Discrepancy)

## 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.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.16.9 |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.16.9 |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.16.9 |

Products: 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.

## Other vulnerabilities in go-ethereum

- [CVE-2026-26314](https://insights.sbomify.com/CVE-2026-26314/): Go Ethereum affected by DoS via malicious p2p message (high 8.7)
- [CVE-2023-42319](https://insights.sbomify.com/CVE-2023-42319/): go-ethereum vulnerable to denial of service via crafted GraphQL query (high 7.5)
- [CVE-2023-40591](https://insights.sbomify.com/CVE-2023-40591/): Denial of service via malicious p2p message in go-ethereum (high 7.5)
- [CVE-2021-42219](https://insights.sbomify.com/CVE-2021-42219/): Denial of service in go-ethereum (high 7.5)
- [CVE-2022-23327](https://insights.sbomify.com/CVE-2022-23327/): Denial of Service in Go-Ethereum (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26315 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-26315 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.16.9
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.16.9
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.16.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26315/ (Markdown: https://insights.sbomify.com/CVE-2026-26315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26315
- OSV: https://osv.dev/vulnerability/CVE-2026-26315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26315/
Summaries are generated and may contain mistakes; the official description above is the record.