Bitcoin Core fixes a node stall bug, found by an AI scan, that used one transaction ID repeated 50,000 times
A peer could freeze a node's message processing, new blocks included, for over a dozen seconds per message. Fixes are in versions 30.5, 31.3 and 32.1; the 29.x line gets none.

Contents
On Friday, November 20, 2026, Bitcoin Core, open-source software used to run Bitcoin nodes, disclosed a medium-severity bug that let a peer temporarily stop a node from processing blocks and transactions. The attack relied on repeating the same transaction ID up to 50,000 times in one message. The flaw was found by an automated scan using a large language model (LLM), according to the project's security advisory.
What the bug did
A node keeps transactions whose parent transactions it has not yet seen in a holding area the project calls the orphanage, and asks peers for the missing parents. Since version 29.0, when a peer announced a transaction that was sitting in the orphanage, the node checked each of that orphan's parents against its mempool, the pool of unconfirmed transactions, and against its records of recently seen transactions, the advisory says.
Peers announce transactions in "inv" messages, which 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 and then repeat that orphan's ID 50,000 times in one message. "Each such message stalls the node for over a dozen seconds," the advisory says. During that time the node processes no messages from any other peer, including new blocks, and further messages could extend the stall.
The fix makes the node process each transaction announced in an inv message only once. The change, pull request 35878 by Gregory Sanders, was merged into the main code on August 6, 2026.
Who found it
The advisory says the issue "was discovered through an automated LLM scan" run as part of Elias Rohrer's Project Loupe at Spiral. Loupe is an open-source tool that runs LLM agents over a codebase and has them check their own findings, for example by writing a test that reproduces the bug, according to its GitHub page. CoinDesk describes Spiral as an open-source development unit of Block.
Sanders validated the Loupe finding and brought it to the Bitcoin Core security team, the advisory says. Its timeline shows Project Loupe reporting the issue on July 8, 2026, and a second researcher, named as Stutxo, reporting it independently on August 4.
Fixed versions and the faster disclosure track
| Version line | Affected versions | Fixed in |
|---|---|---|
| 29.x | 29.0 to 29.5 | No fix (end of life) |
| 30.x | 30.0 to 30.4 | 30.5, November 20, 2026 |
| 31.x | 31.0 to 31.2 | 31.3, November 20, 2026 |
| 32.x | None listed | 32.1, October 27, 2026 |
The 31.3 release notes list the fix as the only network change in that release. The developers rated the bug medium severity and "easily discoverable." Under the project's disclosure policy, that label covers flaws "that can be discovered with minimal effort, such as through a simple LLM prompt." Such bugs get a point release for each maintained major version as soon as possible, together with an advisory, instead of the usual embargo.
Other medium-severity bugs stay undisclosed until two weeks after the last affected version reaches end of life. That is why the project disclosed three other flaws on November 10, about a year after fixing them. The policy defines medium severity as bugs that noticeably degrade a node's performance or functionality but are limited in scope or exploitability. The advisory describes a temporary stall, not a loss of funds.
What it could mean for node operators and exchanges
In our assessment, the main exposure is for businesses that depend on a node seeing new blocks promptly. CoinDesk notes that a stalled node could leave an exchange slow to credit deposits, or a miner working on an outdated view of the chain. With the details now public and no patch coming for 29.x, operators on 29.x or on unpatched 30.x and 31.x releases are running software with a documented flaw; the advisory names 30.5, 31.3 and 32.1 as the fixed versions.
The finding is another case of AI tools in security work; on November 16 Google said it had found an AI tool that wrote and ran exploits. It is also the latest of several security fixes for bitcoin software this month, after BTCPay Server shipped an emergency update for five nginx flaws on November 18. Points to watch are how quickly reachable nodes move to the fixed versions and whether Bitcoin Core publishes more advisories under its faster track for easily discoverable bugs.
Sources
- Bitcoin Core — CVE-2026-117348 - Node stall through duplicate orphan announcements (November 20, 2026)
- Bitcoin Core — Security Advisories (policy and severity classes)
- Bitcoin Core — Bitcoin Core 31.3 release notes (November 20, 2026)
- GitHub (bitcoin/bitcoin) — Pull request 35878: process unique tx INVs only (August 4, 2026)
- GitHub (project-loupe) — Loupe repository README
- CoinDesk — Bitcoin nodes could be stalled by repeating one ID 50,000 times. AI found the bug (November 21, 2026)
This article was researched and drafted with the help of AI tools, checked against its sources in a separate AI fact-check and edit, and approved for publication by Trading Metrics. Read our AI use policy.
This article is for information only and is not financial advice. Crypto assets and leveraged products are volatile and you can lose money. Do your own research and consider your circumstances before trading.