How severe is GHSA-m6j8-rg6r-7mv8?

No CVSS score has been assigned to GHSA-m6j8-rg6r-7mv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m6j8-rg6r-7mv8?

GHSA-m6j8-rg6r-7mv8 affects the following packages: github.com/ethereum/go-ethereum (Go). Ecosystems affected: Go.

How do I fix GHSA-m6j8-rg6r-7mv8?

Update github.com/ethereum/go-ethereum to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6j8-rg6r-7mv8 is resolved across your whole dependency graph.

How do I detect GHSA-m6j8-rg6r-7mv8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ethereum/go-ethereum, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m6j8-rg6r-7mv8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-m6j8-rg6r-7mv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m6j8-rg6r-7mv8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m6j8-rg6r-7mv8?

GHSA-m6j8-rg6r-7mv8 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m6j8-rg6r-7mv8?

GHSA-m6j8-rg6r-7mv8 is classified as CWE-203 (CWE-203). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m6j8-rg6r-7mv8 published, and has it been updated?

GHSA-m6j8-rg6r-7mv8 was published on February 18, 2026 and was last updated on February 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Go Ethereum Improperly Validates the ECIES Public Key in RLPx HandshakeGHSA-m6j8-rg6r-7mv8

Fix: ethereum/go-ethereum#33669

GHSA-m6j8-rg6r-7mv8 is a CWE-203 vulnerability in github.com/ethereum/go-ethereum. A fix is available for github.com/ethereum/go-ethereum — see the affected versions and patch details below.

Also known asCVE-2026-26315GO-2026-4511

Published

Feb 18, 2026

Updated

Feb 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m6j8-rg6r-7mv8.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/ethereum/go-ethereum

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ethereum/go-ethereum`	all versions	1.16.9`go get github.com/ethereum/go-ethereum@v1.16.9`

Affected Products

1 product · 1 configurations

Application

go ethereumethereum

< 1.16.9

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ethereum/go-ethereum, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ethereum/go-ethereum to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6j8-rg6r-7mv8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key. ### Patches The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. We recommend rotating the node key after applying the upgrade, which can be done by removing the file `<datadir>/geth/nodekey` before starting Geth. ### Credit The issue was reported as a public pull request to go-ethereum by @fengjian.