Bitcoin Core Fixes Node-Stall Bug That Repeated One Transaction ID 50,000 Times
Published November 21, 2026, 9:10 PM PKT. Based on Bitcoin Core's security advisory for CVE-2026-117348, published November 20, 2026, and CoinDesk reporting on November 21, 2026.
Bitcoin Core has fixed a flaw that let a single peer temporarily freeze a node by repeating one transaction ID 50,000 times in a single message. The project disclosed the bug, tracked as CVE-2026-117348, on November 20, 2026, and released patched versions 30.5 and 31.3 the same day. Version 32.1, released October 27, already carried the fix. The disclosure said nothing about the flaw being exploited in the wild, and the bug could delay a node, not steal funds or rewrite the chain.
The flaw lived in how Bitcoin Core handles orphan transactions, payments that spend coins from an earlier transaction the node has not seen yet. A node keeps those orphans and asks the peer that announced them for the missing parent transactions. Since version 29.0, when a peer announces an orphan by its transaction ID, Bitcoin Core builds the list of the orphan's missing parents and checks each one against its mempool and its filters of recently seen transactions, to decide whether to ask for them. A single announcement message, called an inv message, can carry up to 50,000 entries, and the software did not skip duplicate entries. An attacker could send a node an orphan with thousands of missing parents, then repeat its ID 50,000 times in one announcement, forcing the node to run the same expensive checks again and again. "Each such message stalls the node for over a dozen seconds," the advisory said, "during which it processes no messages from other peers, including blocks." More messages could stretch the disruption further.
The 50,000-times trick
The attack needed no special access and no computing power, only a peer connection and a crafted message. The attacker first sends an orphan transaction with thousands of missing parents, which makes the parent-checking work expensive. Then the attacker announces that same orphan's ID 50,000 times in one inv message, the maximum a single message can carry. Because the vulnerable software processed every entry instead of skipping repeats, the receiving node repeated the costly parent lookups 50,000 times. Each message froze the node for more than a dozen seconds, and during that window it handled no messages at all, not even new blocks. Repeated messages could keep a node busy indefinitely, which is why the flaw matters for exchanges and miners even though it cannot move coins. An exchange node stuck in that loop could be slow to credit deposits, and a miner working from stale data could waste computing power on an outdated view of the chain.
Which versions are affected
The bug affects versions 29.0 through 29.5, 30.0 through 30.4, and 31.0 through 31.2. Operators on the 30.x line should upgrade to 30.5, and operators on the 31.x line should upgrade to 31.3, both released November 20, 2026. Version 32.1 already includes the fix. The 29.x line has reached end of life and will not receive a patch, so operators still running it need to move to a supported release. The fix itself is a single logical change: each transaction announced in an inv message is now processed only once, so repeating an ID 50,000 times costs no more than announcing it once.
An AI scanner found it in July
The flaw was discovered by an automated scan, not by a human auditor reading the code. Project Loupe, an open-source scanner built by Elias Rohrer at Spiral, Block's open-source development unit, uses AI agents to inspect Bitcoin ($BTC) code, and it reported the issue on July 8, 2026. Gregory Sanders validated the finding and surfaced it to the Bitcoin Core security team. A researcher using the name Stutxo independently reported the same issue on August 4, the same day Sanders opened pull request #35878 with the fix. The pull request was merged into the main codebase on August 6. The fix was backported to the 31.x branch on November 17 in pull request #36892 and to the 30.x branch the same day in pull request #36893, ahead of the November 20 releases and public disclosure.
The new disclosure policy
Bitcoin Core rated the issue medium severity and easily discoverable, and that second label decided how fast it went public. Under a security policy the project adopted on October 22, 2026, flaws considered easily discoverable get fixes across maintained versions as quickly as possible, together with a public advisory. The four-month gap between discovery and disclosure was spent building and testing the fix across the release branches, not hiding the bug. The episode is also a marker for how vulnerability hunting is changing: an AI scanner found a real flaw in the most reviewed codebase in crypto, and a second independent report arrived the same week the fix was written. Node operators running affected versions should upgrade now, since the public advisory tells any attacker exactly how the trick works.
This article is news reporting and is not investment advice.
Sources
- Bitcoin Core, CVE-2026-117348, Node stall through duplicate orphan announcements, November 20, 2026 (primary source: a peer could stop a node from processing blocks and transactions temporarily by repeatedly announcing an orphan transaction with many missing parents; fix released in Bitcoin Core versions 30.5, 31.3 and 32.1; affected versions 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; medium severity and easily discoverable; a single inv message can carry up to 50,000 entries and duplicate entries were not skipped; each such message stalls the node for over a dozen seconds, during which it processes no messages from other peers, including blocks; the fix processes each transaction announced in an inv message only once; discovered through an automated LLM scan as part of Elias Rohrer's Project Loupe at Spiral, validated and surfaced by Gregory Sanders; timeline: Loupe reported July 8, Stutxo independently reported August 4, pull request #35878 opened August 4 and merged August 6, Bitcoin Core 32.1 released October 27 with a fix, backports to 31.x and 30.x on November 17, versions 30.5 and 31.3 released November 20 with public disclosure)
- CoinDesk, Bitcoin developers fix 'medium' bug that could have delayed transactions, November 21, 2026 (secondary source: an AI tool developed at Jack Dorsey's Block discovered the flaw; Bitcoin Core rated the vulnerability medium severity and released fixes in versions 30.5 and 31.3 that ensure each transaction announced in a batch is processed only once; under the security policy adopted October 22, easily discoverable flaws receive fixes across maintained versions as soon as possible, with a public advisory alongside the releases)
MABOnChain Daily Brief
The key crypto and markets stories in one short, plain-language email. Free. Unsubscribe any time.
Prefer chat? Join us on Telegram Watch on YouTube
Keep reading
BTCS Warns the SEC Its $54 Million Aave Loan Could Be Liquidated as Ether Slides
Nasdaq-listed Ether ($ETH) treasury firm BTCS told the U.S. Securities and Exchange Commission it cannot rule out the liquidation of its roughly $54 million loan on Aave, backed by its Ether ($ETH) holdings, after Ether ($ETH) fell toward $1,730. The company cut the debt from about $64 million, but the price drop largely erased the improvement, and its shares fell 12.2 percent on Friday.
Chainflip Halts All Swaps After $4.86 Million Drains From Its Ethereum Vault
Cross-chain swap protocol Chainflip put its protocol into full safe mode on November 21, 2026, halting deposits, withdrawals, swaps and quotes, after about $4.86 million in Ether ($ETH), USD Coin ($USDC) and Tether ($USDT) left its Ethereum ($ETH) vault in a single transaction carrying a valid aggregate signing key signature. Trackers say the funds were swapped into Ether ($ETH) and moved into Tornado Cash within minutes, and Chainflip's FLIP ($FLIP) token fell about 39 percent.
ZebPay Warns Customers After MoEngage Breach Exposes Personal and Account Data
Indian crypto exchange ZebPay warned customers on November 21, 2026 that personal and account activity data was taken in a breach at its communications provider MoEngage, after an unauthorized party used compromised credentials to reach MoEngage's cloud infrastructure. ZebPay says its own wallets, databases and trading systems were unaffected, customer funds are safe, and users should watch for calls, texts and emails that use their personal details to impersonate the exchange.
Binance Has Recovered Just $32 Million of the $6.4 Billion Stolen, With $2.82 Billion Frozen
Three weeks after the October 29, 2026 hack, only $32 million of the $6.4 billion stolen from Binance has actually been recovered, according to blockchain investigator SomaXBT, cited by Wu Blockchain. About $2.82 billion is frozen, $2.67 billion is still in the attackers' hands, and 18,270 Bitcoin ($BTC) taken directly from the exchange has not moved since the night of the theft.



