cve.bz

CVE-2026-26315 ethereum go ethereum: Observable Discrepancy

6.9 mediumEPSS 0.5%Fix available

Medium (6.9) in ethereum go ethereum. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/ethereum/go-ethereum 1.16.9.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-02-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-203 Observable Discrepancy
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-26315 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-26315?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-26315?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-26315 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ethereum:go_ethereumbefore 1.16.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m6j8-rg6r-7mv8Gogithub.com/ethereum/go-ethereum<1.16.91.16.9
GO-2026-4511Gogithub.com/ethereum/go-ethereum<1.16.91.16.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20260226T182644-150000.1.149.1SUSE-SU-2026:0757-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
Alpinev3.23, v3.24geth1.17.0-r0ALPINE-CVE-2026-26315

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE · Alpine.

Attack patterns (CAPEC)

  • CAPEC-189 Black Box Reverse Engineering Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON