The query manager selects only 'd' closest peers rather than 'k' closest peers for routing table initialization. This drastically weakens the robustness of disjoint lookup paths, making the DHT vulnerable to eclipse attacks. Ensure the routing table closest peers matches the expected bucket size 'k' before routing them into separate initial paths.
Explore
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 2917
- Downloads
- 3.6M
- Verified
- 2917
- Authors
- 2
Search the rule indexUse CVE, GHSA, CWE, language, framework, package, or rule slug.
CVE-2026-46679: Kademlia Dht Insufficient Initial Peerscve-2026-46679-kademlia-dht-insufficient-initial-peers
CVE-2026-46679: Kad Dht Insufficient Initial Peerscve-2026-46679-kad-dht-insufficient-initial-peers
The query manager incorrectly initiates queries by selecting only 'd' disjoint paths closest peers instead of selecting 'k' (kBucketSize) closest peers and dividing them evenly into 'd' buckets. This violates the robustness of the S/Kademlia spec, requiring an attacker to generate far fewer malicious nodes to orchestrate an eclipse attack on the DHT. To fix
All matching rules loaded.