---
title: "Bitcoin Core Patches Node Stall Vulnerability Discovered by Spiral's LLM Tool"
description: "A flaw in orphan transaction handling allowed peers to halt block processing for over a dozen seconds per malicious message."
url: https://basisdesk.news/news/bitcoin-core-patches-node-stall-vulnerability-project-loupe
published: 2026-11-20T15:21:16.753Z
modified: 2026-11-20T15:21:16.753Z
section: Security & Hacks
author: Basis Desk Newsroom (AI-generated, source-verified)
sentiment: neutral
tickers: [BTC]
tags: [bitcoin-core, vulnerability, cve-2026-117348, spiral, node-security, open-source]
license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice.
---

# Bitcoin Core Patches Node Stall Vulnerability Discovered by Spiral's LLM Tool

A flaw in orphan transaction handling allowed peers to halt block processing for over a dozen seconds per malicious message.

## At a glance

- **What happened:** Bitcoin Core disclosed CVE-2026-117348 and shipped versions 30.5, 31.3, and 32.1 to resolve a node stall vulnerability.
- **Why it matters:** Malicious peers could repeatedly stall vulnerable nodes for over a dozen seconds, stopping block and transaction validation.
- **Who is affected:** Node operators running Bitcoin Core versions 29.0 through 31.2.
- **Takes effect:** 2026-11-20
- **What's next:** Node operators must update to version 30.5, 31.3, or 32.1, as the 29.x series will receive no further patches.
- **Primary source:** [CVE-2026-117348 - Node stall through duplicate orphan announcements](https://bitcoincore.org/en/2026/11/20/disclose-orphan-inv-stall/) — Bitcoin Core

## Key points

- CVE-2026-117348 allowed attackers to stall Bitcoin Core nodes for over 12 seconds per message via duplicate orphan transaction announcements.
- Fixes are deployed in Bitcoin Core versions 30.5, 31.3, and 32.1, while the 29.x series has reached end-of-life and will receive no patch.
- The vulnerability was identified using Project Loupe, an automated LLM scanning tool developed at Spiral by Elias Rohrer.

## Editorial remark

- **Context:** Bitcoin Core's orphan transaction processing logic introduced in version 29.0 omitted duplicate checks inside 50,000-entry inventory announcements, opening a resource exhaustion path.
- **Impact:** Unpatched node operators running versions 29.0 through 31.2 face temporary processing freezes and block ingestion delays when targeted by adversarial peers.
- **Watch:** Node operator adoption rates for Bitcoin Core releases 30.5, 31.3, and 32.1 across public network telemetry.

Bitcoin Core developers disclosed a medium-severity vulnerability on Nov. 20 tracked as CVE-2026-117348, which permitted malicious network peers to temporarily stall nodes by flooding them with duplicate orphan transaction announcements [1]. The project shipped security updates in versions 30.5, 31.3, and 32.1 to neutralize the bug [1]. The unpatched 29.x release line has reached end-of-life status and will receive no remediation [1]. At the time of writing, $BTC traded down 4.6% over 24 hours at $60,334 amid broad digital asset market declines.

The flaw stemmed from changes introduced in version 29.0 regarding how nodes manage transactions with unconfirmed antecedents [1]. When an incoming transaction references missing inputs, Bitcoin Core holds the data in an internal orphanage and requests missing parents from connected peers [1]. When peers announced transactions via witness transaction identifiers (wtxids), nodes iterated through the orphan's parent inventory, cross-referencing entries against both the local mempool and recent transaction filters [1]. Because network inventory (`inv`) packets can hold up to 50,000 entries and previously failed to filter duplicates, an attacker could repeatedly broadcast an orphan transaction's identifier up to 50,000 times [1]. Processing these inflated messages incapacitated node operations for over a dozen seconds at a time, blocking incoming blocks and ordinary network messages [1].

## Automated Auditing and Coordinated Disclosure

The vulnerability was initially uncovered via an automated large language model scanner under Elias Rohrer’s Project Loupe initiative at Spiral [1]. Spiral researcher Gregory Sanders validated the finding and delivered the report to the Bitcoin Core security team on July 8, 2026 [1]. An independent disclosure by security researcher Stutxo followed on Aug. 4, 2026, prompting Sanders to open pull request #35878, which merged into master two days later [1]. The remediation ensures node software processes each announced transaction identifier in an inventory payload only once [1].

Bitcoin Core backported the vulnerability fix to the 30.x and 31.x maintenance branches on Nov. 17 following the initial public rollout of version 32.1 on Oct. 27 [1]. The disclosure arrives alongside broader ecosystem scrutiny of infrastructure stability and smart contract reliability, reflecting heightened developer attention to protocol-level vectors. Node operators running versions 29.0 through 31.2 must upgrade to maintained patch releases to eliminate the denial-of-service vector [1].

## FAQ

**Which Bitcoin Core versions are affected by the vulnerability?**

Versions 29.0 to 29.5, 30.0 to 30.4, and 31.0 to 31.2 are affected. The flaw has been fixed in versions 30.5, 31.3, and 32.1.

**Will Bitcoin Core version 29.x receive an update?**

No. The 29.x release branch has reached end-of-life status and will not receive security backports.

## Sources

1. [CVE-2026-117348 - Node stall through duplicate orphan announcements](https://bitcoincore.org/en/2026/11/20/disclose-orphan-inv-stall/) — Bitcoin Core, 2026-11-20

---
Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai
