Bitcoin Core released versions 30.5 and 31.3 to fix a medium-severity bug that an AI scanner from Block's Spiral found. The flaw could let an attacker temporarily stop a node from processing network messages by repeating one transaction ID 50,000 times.
An AI tool built by Jack Dorsey's Block found a way to temporarily stop a bitcoin node from processing messages from the network. The trick feeds the node one transaction ID, repeated 50,000 times.
Bitcoin Core disclosed the bug on Friday as CVE-2026-117348 and released versions 30.5 and 31.3 with fixes. The advisory credits an automated AI scan run through Elias Rohrer's Project Loupe at Spiral, Block's open-source development unit.
How one repeated ID stalls a node
A node holds on to orphan transactions, which spend coins from an earlier transaction the node has not seen yet. Since version 29.0, when another node announces an orphan, the software builds a list of its missing parent transactions and checks its records before deciding what to request.
Nodes announce transactions in batches of up to 50,000 entries, and the software did not skip repeated entries. An attacker could first send an orphan transaction with thousands of missing parents, then repeat its ID 50,000 times in one announcement, so the receiving node would run the expensive checks over and over.
According to the advisory, "Each such message stalls the node for over a dozen seconds". During that time the node processes no messages from other nodes, including new blocks, and further messages could prolong the disruption.
Possible effects and the fix
An exchange relying on an affected node could be delayed in crediting deposits, while a miner could waste computing power working on an outdated view of the blockchain. Core developers rated the bug as medium severity and easily discoverable.
Under the security policy it adopted on Oct. 22, easily discoverable flaws receive fixes across maintained versions as soon as possible, with a public advisory alongside the releases. The fix makes the node process each transaction announced in a batch only once.
However, the retired 29.x branch will not get a fix, according to The Defiant.
Sources: CoinDesk, The Defiant (snippet-based)
Trading involves risk.