An uncontrolled resource consumption issue allows remote P2P peers to exhaust blocking-pool threads. This occurs when attackers send `getblocks` or `getheaders` messages containing oversized block locator vectors with up to 65,535 locator hashes. This action triggers per-hash chain lookups, which degrades the performance of block validation, RPC, and the mempool.