Bitcoin Core on Friday disclosed a medium-severity vulnerability that could let a connected peer temporarily stop a node from processing blocks and transactions. The advisory, published November 20 as CVE-2026-117348 and titled “Node stall through duplicate orphan announcements,” says a fix was released in versions 30.5, 31.3 and 32.1. Version 32.1 already shipped with the patch on October 27; Friday’s 30.5 and 31.3 releases brought the same fix to the maintained 30.x and 31.x lines. The advisory does not describe a way to steal coins, and the fix sits in the software’s peer-to-peer message handling, not in Bitcoin’s consensus rules. It is also a different bug from a high-severity Bitcoin Core issue disclosed earlier this month.
How the stall works
A peer, the advisory says, “could stop a node from processing blocks and transactions temporarily by repeatedly announcing an orphan transaction with many missing parents.” Bitcoin Core keeps transactions whose parents it has not yet seen, which it calls orphans, and asks peers that announce an orphan for the missing parents. Since version 29.0, when a peer announces a transaction by wtxid and that transaction is already in the orphanage, the software builds the list of the orphan’s parents and checks each one against its mempool and against filters of recently seen transactions.
A single inv message can carry up to 50,000 entries, “and duplicate entries were not skipped.” 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 which it processes no messages from other peers, including blocks.” The advisory does not give a maximum outage if further messages are sent, and it does not say the bug has been used in the wild. “The issue was fixed by processing each transaction announced in an inv message only once.”
Which versions are patched
The advisory calls the issue “Medium severity and easily discoverable.” Affected versions are “29.0 to 29.5, 30.0 to 30.4 and 31.0 to 31.2.” “The 29.x series has reached end of life and will not receive a fix.” Anyone running 32.1, released October 27, already has the fix. For 29.x users, the only patched route is a newer major version.
The 31.3 release notes, also dated November 20, list the notable change as “#35878 net_processing: process unique tx INVs only.” The notes describe the release as including “various bug fixes and performance improvements, as well as updated translations.” The 30.5 notes, published the same day, list the same pull request as a notable change. The public disclosure came with those two releases, after the fix was backported to the 31.x and 30.x branches on November 17.
How the bug was found
The advisory says the issue “was discovered through an automated LLM scan, as part of Elias Rohrer’s Project Loupe at Spiral.” “The Loupe finding was validated and surfaced to the Bitcoin Core security team by Gregory Sanders.” Stutxo independently reported the issue on August 4, the same day Sanders opened pull request #35878. That pull request was merged into the project’s master branch on August 6. Project Loupe had reported the issue on July 8.
That explains the gap between the October fix and Friday’s disclosure. The 32.1 release notes say that under the project’s security policy, “any easily discoverable vulnerabilities fixed in this release will be disclosed as soon as fixed releases are available for all maintained major versions.” For this bug, that point came with the 30.5 and 31.3 releases on Friday. CoinDesk, in a Saturday write-up, said an exchange relying on an affected node could be delayed in crediting deposits, and that a miner could work from an outdated view of the chain. Those examples are CoinDesk’s, not wording from the official advisory. The advisory itself confines the effect to a temporary stall in processing blocks and transactions, including new blocks.
What to watch next is whether operators still on 30.0 through 30.4 or 31.0 through 31.2 move to 30.5 or 31.3, and whether anyone reports the bug being used in the wild.
FAQ
Can this bug be used to steal bitcoin? The advisory does not say so. It describes a temporary stall in processing blocks and transactions, not a consensus change and not a method for moving coins.
Which Bitcoin Core versions need an update? A fix is in 30.5, 31.3 and 32.1. Versions 30.0 to 30.4 and 31.0 to 31.2 are affected and can be upgraded. Versions 29.0 to 29.5 are also affected, but the 29.x series is at end of life and will not receive a fix.
Is this the same as the high-severity Bitcoin Core bug disclosed in November? No. The earlier disclosure involved a different CVE and a different problem with block templates. This advisory is CVE-2026-117348 and concerns duplicate orphan announcements.
Disclaimer: This article is for informational purposes only and does not constitute financial advice.

















