GHSA-MQ3P-RRMP-79JG
Vulnerability from github – Published: 2026-01-13 21:55 – Updated: 2026-01-13 21:55
VLAI?
Summary
go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message
Details
Impact
An attacker can cause high CPU usage by sending a specially crafted p2p message. More details to be released later.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by @Yenya030
Severity ?
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.16.7"
},
"package": {
"ecosystem": "Go",
"name": "github.com/ethereum/go-ethereum"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.16.8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-22868"
],
"database_specific": {
"cwe_ids": [
"CWE-20",
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-13T21:55:29Z",
"nvd_published_at": "2026-01-13T21:15:54Z",
"severity": "HIGH"
},
"details": "**Impact**\n\nAn attacker can cause high CPU usage by sending a specially crafted p2p message.\nMore details to be released later.\n\n**Credit**\n\nThis issue was reported to the Ethereum Foundation Bug Bounty Program by @Yenya030",
"id": "GHSA-mq3p-rrmp-79jg",
"modified": "2026-01-13T21:55:29Z",
"published": "2026-01-13T21:55:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ethereum/go-ethereum/security/advisories/GHSA-mq3p-rrmp-79jg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22868"
},
{
"type": "WEB",
"url": "https://github.com/ethereum/go-ethereum/commit/abeb78c647e354ed922726a1d719ac7bc64a07e2"
},
{
"type": "PACKAGE",
"url": "https://github.com/ethereum/go-ethereum"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…