# CVE-2026-26313: GO-2026-4508 - Go Ethereum affected by DoS via malicious p2p message in github.com/ethereum/go-ethereum

Source: https://junglewise.ai/threats/cve-2026-26313-go-ethereum-affected-by-dos-via-malicious-p2p-message  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-24  
License: CC BY 4.0 with a link back

CVE-2026-26313 · Severity: medium · CVSS 4 · Published 2026-02-24

Go Ethereum affected by DoS via malicious p2p message in github.com/ethereum/go-ethereum

Technologies: [github.com/ethereum/go-ethereum (Go)](https://junglewise.ai/threats/technologies/github-com-ethereum-go-ethereum). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-26313 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-26313 being exploited in the wild.

**How severe is CVE-2026-26313?** Medium severity, with a CVSS score of 4, published 24 February 2026.

**Which products and versions are affected?** github.com/ethereum/go-ethereum (Go) SEMVER:introduced=0,fixed=1.17.0.

**Is there a fix for CVE-2026-26313?** Yes. github.com/ethereum/go-ethereum (Go): upgrade to 1.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-26313?** Check whether you run github.com/ethereum/go-ethereum (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/ethereum/go-ethereum (Go): upgrade to 1.17.0 or later

  ```sh
  go get github.com/ethereum/go-ethereum@v1.17.0
  ```


## Affected products

- github.com/ethereum/go-ethereum (Go) SEMVER:introduced=0,fixed=1.17.0

## Identifiers

- CVE-2026-26313
- GHSA-689v-6xwf-5jf3
- GO-2026-4508

## Related threats

- [GO-2026-4511 - Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake in github.com/ethereum/go-ethereum](https://junglewise.ai/threats/cve-2026-26315-go-ethereum-improperly-validates-the-ecies-public-key-in-rlpx)
- [GO-2026-4507 - Go Ethereum affected by crash via malicious p2p message in github.com/ethereum/go-ethereum](https://junglewise.ai/threats/cve-2026-26314-go-ethereum-affected-by-dos-via-malicious-p2p-message)
- [GO-2026-4315 - DoS via malicious p2p message affecting a vulnerable node in github.com/ethereum/go-ethereum](https://junglewise.ai/threats/cve-2026-22862-go-ethereum-is-vulnerable-to-dos-via-malicious-p2p-message)
- [GO-2026-4314 - High CPU usage leading to DoS via malicious p2p message in github.com/ethereum/go-ethereum](https://junglewise.ai/threats/cve-2026-22868-go-ethereum-is-vulnerable-to-high-cpu-usage-leading-to-dos-via)
- [GO-2025-3436 - Go Ethereum vulnerable to DoS via malicious p2p message in github.com/ethereum/go-ethereum](https://junglewise.ai/threats/cve-2025-24883-go-ethereum-vulnerable-to-dos-via-malicious-p2p-message)