Key Highlights
- An automated AI tool from Block’s open-source division, Spiral, identified a vulnerability that could temporarily freeze message processing on Bitcoin nodes.
- Bitcoin Core officially disclosed the flaw as CVE-2026-117348, deploying fixes across software versions 30.5 and 31.3.
- Core developers designated the bug as “medium severity” and “easily discoverable,” prompting rapid remediation under a disclosure framework established on Oct. 22.
AI Scanner Uncovers Bitcoin Core Node Vulnerability
An automated artificial intelligence tool developed by Jack Dorsey’s financial technology company, Block, has detected a denial-of-service vulnerability capable of temporarily halting Bitcoin nodes from processing incoming network communications. Bitcoin Core, the primary open-source software implementation underpinning the Bitcoin network, formally disclosed the security issue under the tracking identifier CVE-2026-117348 and released software versions 30.5 and 31.3 containing the necessary patches.
According to reporting from CoinDesk, the official advisory attributes the discovery to an automated AI scan executed via Elias Rohrer’s Project Loupe. The initiative operates under Spiral, the dedicated open-source development arm of Block. Nodes—the distributed computers responsible for validating transactions, verifying blocks, and relaying ledger data across the global peer-to-peer network—serve as the foundational backbone of Bitcoin’s operational integrity.
How the Repeated Transaction Exploit Stalled Nodes
The mechanics of the exploit center around how Bitcoin nodes process pending ledger updates. Under normal operating conditions, Bitcoin nodes maintain a backlog of orphan transactions—validly formatted payments that attempt to spend coins originating from a parent transaction that the specific node has not yet observed or processed. When encountering an orphan transaction, the node temporarily retains it and actively queries peers to locate the missing transaction data.
Project Loupe’s scan revealed that an attacker could disrupt this mechanism by feeding a target node a single transaction identifier repeated 50,000 times. By overloading the node’s messaging and resolution pipeline with this massive sequence of identical requests, the software was rendered temporarily incapable of handling standard messages broadcast across the network.
Developer Classification and Rapid Remediation
Following the disclosure, Bitcoin Core developers assessed the flaw and rated the bug as “medium severity” and “easily discoverable.” Under an updated operational security policy formally adopted by the project on Oct. 22, vulnerabilities designated as easily discoverable mandate immediate patch engineering across all actively maintained software versions, accompanied by an immediate public advisory alongside the rollout.
Why This Matters
The real-world ramifications of a node denial-of-service attack on Bitcoin infrastructure can be severe. If a cryptocurrency exchange operates an affected node, any temporary processing pause could introduce significant delays in verifying and crediting customer deposits. Similarly, cryptocurrency miners relying on an impaired node could end up expending substantial computational power working on an obsolete or outdated view of the blockchain, resulting in wasted hash power and lost block rewards. Furthermore, the incident highlights the expanding utility of automated AI scanning systems like Project Loupe in identifying edge-case software bugs across foundational blockchain protocols before malicious actors can exploit them in the wild.
Frequently Asked Questions
What is CVE-2026-117348?
CVE-2026-117348 is a Bitcoin Core vulnerability discovered by Block’s Spiral team using an AI tool. It allowed an entity to temporarily stall a node’s message-processing capabilities by submitting 50,000 repetitions of a single transaction ID.
Which versions of Bitcoin Core resolve the issue?
Bitcoin Core developers resolved the vulnerability by shipping patches in versions 30.5 and 31.3 alongside a formal security advisory.
How could the bug affect miners and cryptocurrency exchanges?
A disrupted node can delay an exchange from recognizing user transaction deposits in a timely manner. For miners, a stalled node risks causing mining rigs to direct computational energy toward stale chain data rather than the most recent block.




