Bitcoin Core has disclosed and patched a denial-of-service flaw that could temporarily stop an affected node from processing transactions, blocks and other peer messages. The project published its advisory for CVE-2026-117348 on November 20, rating the issue medium severity and easily discoverable. Fixes are included in Bitcoin Core 30.5, 31.3 and 32.1. The disclosure concerns a patched software weakness, not evidence of an attack on the Bitcoin network.
How duplicate announcements caused the stall
The bug involved Bitcoin Core's handling of orphan transactions, which reference parent transactions that a node has not yet received. Since version 29.0, when a peer announced an orphan already held by a node, the software assembled the orphan's missing parents and checked them against the mempool and recently seen transaction filters before deciding what to request. A single inventory message can contain as many as 50,000 entries, but the affected code did not skip duplicates.
Related reporting: Bitcoin Core Ships Multi-Version Fixes for Three AI-Found Node Flaws
According to the Bitcoin Core advisory, an attacker could first send an orphan with thousands of missing parents and then repeat that orphan's witness transaction identifier 50,000 times in an inventory message. The node would redo the same parent checks for every duplicate. One such message could stall it for more than a dozen seconds, during which it would not process messages from other peers, including new blocks. Additional crafted messages could extend the disruption.
What the fix changes
The repair makes Bitcoin Core process each transaction announced in an inventory message only once. The project says versions 29.0 through 29.5, 30.0 through 30.4 and 31.0 through 31.2 are affected. Operators on maintained branches can update to 30.5, 31.3 or 32.1. Version 32.1 had already incorporated the fix when it was released on October 27; the 30.x and 31.x backports arrived on November 20. The 29.x line is end of life and will not receive this correction.
Why node operators should pay attention
A temporary processing stall does not alter Bitcoin's supply rules or let an attacker spend coins they do not own, but it can interfere with services that depend on a timely node view. CoinDesk noted that an exchange using an affected node could credit deposits more slowly, while a miner could briefly work from stale chain information. Those are possible operational consequences, not confirmed incidents. The advisory did not report known exploitation, so the practical response is to assess deployed versions and update rather than treat the disclosure as a network emergency.
An AI-assisted finding with human validation
Bitcoin Core credited the initial discovery to an automated large-language-model scan conducted through Elias Rohrer's Project Loupe at Spiral. Gregory Sanders validated the result and brought it to the security team. Project Loupe reported the issue on July 8, and a researcher identified as Stutxo independently reported it on August 4. Sanders opened the fix that day, and it was merged on August 6. The sequence shows automated review contributing to discovery while human researchers and maintainers handled validation, remediation and disclosure.
The disclosure policy behind the timing
Bitcoin Core's security policy treats easily discoverable flaws differently from vulnerabilities that benefit from a longer embargo. Because simple automated tools may reproduce such findings cheaply, maintained releases can receive fixes and a public advisory without the normal severity-based delay. CVE-2026-117348 is a concrete example of that approach: the project coordinated backports, released point versions and then disclosed the mechanics. Operators still need normal deployment checks, including confirming that production nodes have restarted on the patched binary.
Sources
- CVE-2026-117348 - Node stall through duplicate orphan announcements
- Bitcoin Core Security Advisories
- Bitcoin nodes could be stalled by repeating one ID 50,000 times. AI found the bug
AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.
