Bitcoin Core fixes node stall bug found by an AI scan
Bitcoin Core has disclosed and patched a bug that let one peer freeze a node for over a dozen seconds per message, and the project’s own advisory shows how long the fix took to reach older release branches.
- CVE-2026-117348 affects Bitcoin Core 29.0 to 29.5, 30.0 to 30.4 and 31.0 to 31.2, and is fixed in 30.5, 31.3 and 32.1.
- The flaw was first reported on July 8 by Project Loupe, an automated LLM scan run at Spiral, and independently reported on August 4.
- The advisory does not say the bug was exploited, and it lists no fix for the 29.x series.
The advisory describes a denial-of-service flaw, not a threat to funds
The Bitcoin Core project published the advisory on November 20, 2026. It says a peer could temporarily stop a node from processing blocks and transactions by repeatedly announcing an orphan transaction with many missing parents. Nothing in the advisory describes a risk to coins, signatures or consensus rules. The effect is that a targeted node stops listening for a while.
Orphans are transactions whose parent transactions a node has not yet seen. Bitcoin Core holds them in an orphanage and asks any peer that announces an orphan for the missing parents. The advisory says an attacker could send a node an orphan with thousands of missing parents, then send inv messages repeating its wtxid 50,000 times. Each such message stalls the node for over a dozen seconds. During that time the node processes no messages from other peers, blocks included.
The advisory says the fix processes each transaction announced in an inv message only once. Outlets covering the disclosure add that inv messages can carry up to 50,000 entries and that vulnerable versions did not skip duplicates. Some also trace the weakness to orphan-announcement handling added in version 29.0. That detail comes from press reports. It is not in the portion of the advisory we reviewed.
Three release branches were affected and two got patches on disclosure day
The advisory lists affected versions as 29.0 to 29.5, 30.0 to 30.4 and 31.0 to 31.2. Fixes ship in 30.5, 31.3 and 32.1. The 29.x series is not on the list of fixed releases. Press reports say that branch is no longer supported and will not get a patch. Operators still running 29.x have no fixed release on that branch, so the practical remedy is moving to a supported version.
Node operators on the 30.x and 31.x lines should move to 30.5 or 31.3 respectively. Anyone already on 32.1 has the fix. Version 32.1 was released on October 27, per the advisory’s timeline. That means the newest branch was patched weeks before the older ones, and before the public knew why.
The timeline shows a gap of more than four months between report and disclosure
The advisory publishes a dated sequence. Project Loupe reported the issue on July 8. On August 4, a researcher listed as Stutxo reported it independently, and Gregory Sanders opened pull request 35878 with a fix the same day. That change was merged into the master branch on August 6.
The fix then reached released software in stages. Bitcoin Core 32.1 came out on October 27. Backports to the 31.x and 30.x branches were made on November 17 in pull requests 36892 and 36893. Versions 30.5 and 31.3 were released on November 20, the same day as public disclosure. From first report to disclosure is 135 days.
That is typical of a coordinated process for a medium-severity issue, though the advisory excerpt we reviewed does not explain the reasoning behind the pacing. Press accounts say the project rated the bug medium severity and easily discoverable under a security policy adopted on October 22. They say that policy calls for prompt patches across maintained versions and a public announcement. We could not confirm the policy wording from the advisory itself, so treat that as reported context.
An AI scan found it, and a human then fixed it
The advisory says the issue was discovered through an automated LLM scan, as part of Elias Rohrer’s Project Loupe at Spiral. CoinDesk reported that Spiral is Block’s open-source development unit. The advisory also shows that humans carried the fix. Sanders wrote the patch, and a second researcher found the same flaw independently within a month.
The independent report matters for how the bug should be read. When two parties find the same weakness separately, it suggests the bug was reachable by anyone who looked closely at orphan handling. The “easily discoverable” label reported by the press points the same way. It does not show anyone used it against the network.
What operators and exchanges should check, and what is still unknown
The stall is per message and temporary. CoinDesk reported that an attacker could prolong the disruption by sending further messages, and that the consequences could include delayed exchange deposits or miners working with outdated chain data. Those scenarios are CoinDesk’s interpretation. The advisory only states that a stalled node processes no messages from other peers, including blocks. Any service that relies on a single Bitcoin Core node for deposit crediting or block templates is the type of setup that would feel a stall most. Nodes behind several peers or backed by redundant infrastructure would be less exposed.
Several questions remain open. The advisory excerpt does not say whether the bug was used on the live network. It does not estimate how many nodes ran affected versions, and it gives no workaround other than upgrading. It also does not say how many 29.x nodes are still online. Readers can check the full advisory for any updates on those points.
For now, the practical step is simple: confirm which Bitcoin Core version your node runs, and upgrade to 30.5, 31.3 or 32.1 as appropriate.
Sources
- Bitcoin Core: CVE-2026-117348, Node stall through duplicate orphan announcements
- CoinDesk: Bitcoin developers fix ‘medium’ bug that could have delayed transactions
From the CCS interview archive
All 1,000+ interviews
Diego Di Tommaso on OVER's AR metaverse technology and web3 collaborationDiego Di Tommaso, OVER · Aug 2022
Jag Sidhu discusses DAOs and decentralized governance on SyscoinJag Sidhu, Syscoin · May 2022
Reeve Collins on smart NFTs and the next generation of digital assetsReeve Collins, BLOCKv · May 2022


