CVE-2023-26248
Description
The Kademlia DHT (go-libp2p-kad-dht 0.20.0 and earlier) used in IPFS (0.18.1 and earlier) assigns routing information for content (i.e., information about who holds the content) to be stored by peers whose peer IDs have a small DHT distance from the content ID. This allows an attacker to censor content by generating many Sybil peers whose peer IDs have a small distance from the content ID, thus hijacking the content resolution process.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
CVE-2023-26248 allows Sybil attacks on IPFS Kademlia DHT, enabling content censorship by hijacking content resolution for less than $100.
Vulnerability
CVE-2023-26248 affects the Kademlia DHT implementation in go-libp2p-kad-dht (0.20.0 and earlier) and IPFS (0.18.1 and earlier). The DHT assigns routing information for content to peers whose peer IDs have a small XOR distance from the content ID. This deterministic mapping allows an attacker to generate many Sybil peers with IDs close to a target content ID, thereby monopolizing the set of peers responsible for storing that content's provider records [1][4].
Exploitation
An attacker can exploit this by creating a large number of Sybil (fake) peers in the IPFS network. The adversary only needs to generate peer IDs that are a small DHT distance from the content ID they wish to censor. The attack is practical with minimal effort and cost—research estimates it can be executed for under $100, requiring only a modest number of Sybil nodes to succeed [4]. The attack does not require prior authentication or special privileges beyond the ability to join the IPFS network.
Impact
Successful exploitation allows the attacker to hijack the content resolution process. When other peers request the provider records for a targeted content ID, the attacker's Sybil nodes respond, preventing legitimate providers from being discovered. This effectively censors the content, making it unreachable via the DHT. The attack undermines IPFS's core promise of decentralized, resilient content retrieval [1][4].
Mitigation
The vulnerability has been addressed in later versions of both go-libp2p-kad-dht and IPFS. A Go vulnerability entry (GO-2024-3218) references the issue [3]. The research paper proposes effective detection and mitigation mechanisms achieving 100% mitigation of detected attacks with minimal overhead [4]. Users are advised to update to patched versions (go-libp2p-kad-dht beyond 0.20.0 and IPFS beyond 0.18.1) as soon as possible.
AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/libp2p/go-libp2p-kad-dhtGo | <= 0.20.0 | — |
Affected products
1- Range: <= 0.20.0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-mqr9-hjr8-2m9wghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2023-26248ghsaADVISORY
- arxiv.org/abs/2307.12212nvdWEB
- pkg.go.dev/vuln/GO-2024-3218ghsaWEB
News mentions
0No linked articles in our index yet.