CVE-2026-26313
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedgo-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. Prior to version 1.17.0, an attacker can cause high memory usage by sending a specially-crafted p2p message. The issue is resolved in the v1.17.0 release.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencego-ethereum (geth) versions prior to 1.17.0 contain a denial-of-service vulnerability in the p2p networking layer where an attacker can send a specially-crafted message causing excessive memory consumption, potentially crashing affected nodes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.17.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed geth versionRun 'geth version' or 'geth --version' from command line to display the version numberAffected if Version is below 1.17.0 (e.g., 1.16.x, 1.15.x, etc.)
-
Confirm p2p networking is enabledInspect running geth configuration or startup flags. Look for absence of '--p2p.disabled' or '--maxpeers 0' flags which would disable p2p connectivityAffected if P2p networking is enabled (default behavior) and the node accepts connections from untrusted network peers
-
Verify node is reachable from untrusted networksCheck network configuration: review '--nat' flag setting (e.g., 'extip' makes the node publicly reachable), firewall rules, and whether the node is running on a public IP or behind proper network segmentationAffected if Node is accessible from untrusted peers (e.g., running with default p2p settings on a public IP address)
A user is affected if their geth version is below 1.17.0 AND p2p networking is enabled with exposure to untrusted peers
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.17.0
Upgrade go-ethereum (geth) to version 1.17.0 or later. If immediate upgrade is not feasible, consider implementing p2p message rate limiting or network segmentation to reduce exposure to untrusted peers.
1.17.0
- 1. Backup your node data and configuration files before proceeding
- 2. Stop the running geth service/process
- 3. Download Go Ethereum version 1.17.0 from the official repository (github.com/ethereum/go-ethereum)
- 4. Install the upgraded geth binary or verify your package manager installs version 1.17.0
- 5. Restart the geth service
- 6. Verify the running version is 1.17.0 using: geth version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data