CVE-2026-26314: GO-2026-4507 - Go Ethereum affected by crash via malicious p2p message in github.com/ethereum/go-ethereum

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

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

Technologies: github.com/ethereum/go-ethereum (Go). Vendors: Go.

Quick answers

Is CVE-2026-26314 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-26314 being exploited in the wild.
How severe is CVE-2026-26314?
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.16.9.
Is there a fix for CVE-2026-26314?
Yes. github.com/ethereum/go-ethereum (Go): upgrade to 1.16.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-26314?
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.16.9 or later
    go get github.com/ethereum/go-ethereum@v1.16.9

Affected products

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

Identifiers

  • CVE-2026-26314
  • GHSA-2gjw-fg97-vg3r
  • GO-2026-4507

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.