A disclosure of temporary node stalls
Bitcoin Core disclosed a node-stalling vulnerability on Nov. 20, 2026, saying a peer could temporarily prevent a node from processing blocks and transactions by repeatedly announcing an orphan transaction with many missing parent transactions.
The project’s disclosure characterizes the issue as Medium severity and easily discoverable. It describes a potential disruption to an affected node, not a reported network-wide outage.
Why duplicate announcements mattered
According to Bitcoin Core, an inv message can contain up to 50,000 entries, and duplicate entries were not skipped. In the described scenario, an attacker could first send an orphan transaction with thousands of missing parents, then send inv messages repeating that transaction’s wtxid 50,000 times in each message.
Bitcoin Core says each such message could stall the node for over a dozen seconds. During that time, the node would process no messages from other peers, including blocks.
Affected releases and fixes
Bitcoin Core lists versions 29.0–29.5, 30.0–30.4 and 31.0–31.2 as affected. The project says versions 30.5, 31.3 and 32.1 include a fix.
The project says the 29.x series is end-of-life and will not receive a fix. The change prevents repeated work by processing each transaction announced in an inv message only once.
How the issue was found
Bitcoin Core says the issue was found through an automated LLM scan in Elias Rohrer’s Project Loupe at Spiral. The disclosure credits Gregory Sanders with validating the finding and bringing it to the Bitcoin Core security team.