Bitcoin Core 30.5 and 31.3 patch node-stall CVE
Bitcoin Core released versions 30.5 and 31.3 to patch CVE-2026-117348, a medium-severity DoS vulnerability affecting 14 versions of the software.
November 20. Bitcoin Core shipped 30.5 and 31.3 alongside public disclosure of CVE-2026-117348, a medium-severity vulnerability that could temporarily stop a node from processing blocks and transactions. The Bitcoin Core advisory describes the attack path: a peer repeatedly announces an orphan transaction with many missing parents, forcing the node to work the same path over and over.
The two new releases are Bitcoin Core 30.5 and Bitcoin Core 31.3. The advisory also notes that version 32.1, released October 27, already carried the fix — the November 20 releases finished delivering it to the 30.x and 31.x branches.
Fourteen versions are affected: 29.0 through 29.5 (six releases), 30.0 through 30.4 (five), and 31.0 through 31.2 (three). The 29.x series has hit end of life and won’t receive a patch, so operators still on that branch face a full branch-level upgrade, not a targeted fix arriving on some later date.
The vulnerability traces back to BTC$58,528.00▼6.00% Core 29.0, when the software began holding transactions in its orphanage whose parents it hadn’t yet seen. A singleinv message can carry up to 50,000 entries. By repeatedly announcing an orphan with many missing parents, an attacker could force a node to reprocess the same transaction path — the advisory says that could stall a node for over a dozen seconds per message, cutting off normal block and transaction handling for that window.
The advisory says the fix processes each transaction announced in aninv message only once. Gregory Sanders opened PR #35878 on August 4, it merged into master on August 6, and backports to the 31.x and 30.x branches landed November 17, three days before the public release.
The vulnerability was found through an automated LLM scan run under Elias Rohrer’s Project Loupe at Spiral. Sanders, identified by Bitcoin Core as part of its security team, validated the Loupe finding and brought it to the security team. Stutxo independently reported the same issue on August 4 — the same date Sanders opened the fix pull request.
Version 32.1 had the fix since October 27, but users on 30.x and 31.x branches didn’t get their corresponding releases until November 20. Anyone still on one of the 14 affected versions needs to upgrade; 29.x users have no patch coming and must leave that series entirely.
Bitcoin Core classifies CVE-2026-117348 as medium severity and easily discoverable. The fact sheet describes the impact as a temporary interruption of node availability and block and transaction processing; it does not establish whether the vulnerability was exploited.
A GitHub release entry timestamps version 31.3 at 11:29 on November 20.