TLDR
- Bitcoin Core disclosed a medium-severity bug, CVE-2026-117348, on Nov. 20
- One crafted message could stall a node for more than 12 seconds
- An AI security project called Project Loupe found the flaw
- Fixes are in versions 30.5, 31.3 and 32.1
- The bug cannot steal bitcoin or permanently damage nodes
Bitcoin Core developers disclosed a medium-severity security flaw on Friday, Nov. 20, 2026. The bug is tracked as CVE-2026-117348 and is titled “Node stall through duplicate orphan announcements.” It could stop a node from handling blocks and transactions for a short time.
⚠️ SECURITY: AI just caught a bug in Bitcoin Core that could have frozen Bitcoin nodes, and it's already fixed.
An attacker could have stalled nodes by repeating one transaction ID 50,000 times, delaying blocks and deposits. Jack Dorsey's Block found it with an AI scanner, and… pic.twitter.com/lmka3sy8tx
— CryptosRus (@CryptosR_Us) November 22, 2026
The flaw affected versions 29.0 through 29.5, 30.0 through 30.4, and 31.0 through 31.2. Patched versions are available in 30.5, 31.3 and 32.1. The older 29.x branch is no longer supported and will not get a fix.
How The Bug Worked
Bitcoin Core keeps a holding area called the orphanage. It stores transactions that are waiting on missing parent transactions. When a peer announces one of these transactions, the node checks which parents it needs to request.
The software did not filter out repeated announcements. A single inventory message can hold up to 50,000 entries. An attacker could name the same orphan transaction again and again, and each time the node repeated the same costly check.
Each crafted message could delay a node by more than 12 seconds. During that time, the node could not process new blocks or other network traffic. The advisory said the effect was temporary.
The advisory did not describe any way to steal bitcoin. It also did not describe any way to cause lasting damage to a node. The fix makes the software process each unique announcement only once per inventory message.
Who Found It And When
Project Loupe found the flaw. Elias Rohrer built the project at Spiral, the open-source Bitcoin development arm of Block. It uses large language models to look for security problems in code.
Bitcoin Core developer Gregory Sanders checked the finding and passed it to the security team. Project Loupe reported the issue on July 8. A researcher known as Stutxo filed a separate report on Aug. 4.
Sanders opened a fix on Aug. 4, the same day as the second report. Developers merged it on Aug. 6. Bitcoin Core 32.1 shipped with the fix on Oct. 27.
AI Finds Other Crypto Flaws
Other crypto projects have seen similar AI-assisted findings this year. In February, a review found a critical signature-checking weakness in a proposed XRP Ledger amendment before it went live. A separate probe found a high-severity bug in Nethermind, an Ethereum execution client.
In late May, researcher Taylor Hornby used an AI auditing system to find a four-year-old flaw in Zcash’s Orchard protocol. It could have allowed counterfeit ZEC. Developers fixed it before it was made public.
In August, 16 volunteer developers in a Bitcoin security effort produced 4,962 findings across 390 projects in about one day. Of those, 85 were first rated critical. Maintainers then had to check each report by hand, and many were false positives.
Core Lightning developers also received a flood of AI-written reports. Some of them pointed to real problems that needed fixes.
Bitcoin Core changed its disclosure policy in October. Bugs that are easy to find with simple LLM analysis are now announced when the patched releases come out. CVE-2026-117348 followed that approach.







