AI Finds Bitcoin Node Bug Triggered by 50,000 Repeated IDs

On Friday, Bitcoin Core deployed essential patches to resolve a vulnerability discovered by Loupe, an open-source auditing tool created by Block’s Spiral that utilizes AI agents to inspect Bitcoin code.
An AI utility developed by Jack Dorsey’s Block uncovered a method to briefly halt a Bitcoin node from handling network traffic by sending a single transaction ID, duplicated 50,000 times.
Bitcoin Core, the software powering those network nodes, publicly reported the flaw as CVE-2026-117348 on Friday and rolled out patched versions 30.5 and 31.3.
Nodes are individual machines that verify Bitcoin payments while relaying transactions and blocks across the network.
The real-world fallout of this vulnerability was extensive: an exchange depending on a compromised node might face delays when crediting user deposits, while a miner could squander computing resources processing an obsolete version of the blockchain.
How the Bitcoin Node Vulnerability Could Be Exploited
Bitcoin nodes retain orphan transactions—payments spending coins from prior transactions not yet observed by the machine—before searching for the missing data.
Starting with version 29.0, whenever a peer flags one of these orphans, Bitcoin Core compiles a list of its missing parent transactions and reviews its records before determining what data is needed.
Network nodes broadcast transactions in batches reaching up to 50,000 entries, yet duplicate listings were not filtered out by the software.
A malicious actor could initially transmit an orphan transaction containing thousands of missing parents, before repeating its ID 50,000 times within a single announcement. Consequently, those resource-heavy verification checks would be executed repeatedly by the receiving node.
“Each such message stalls the node for over a dozen seconds,” the advisory said. During that time, it processes no messages from other nodes, including new blocks. Sending further messages could prolong the disruption.
The updated patch ensures that every transaction announced within a batch is processed by the node just once.
This policy stems from developers’ concerns that AI tools let attackers cheaply uncover certain vulnerabilities, eroding the safety previously gained when patches were kept quiet.
This article follows our editorial policy. Spotted an error? Request a correction. Not financial advice.


