• Bitcoin Core disclosed CVE-2026-117348 on Nov. 20: a peer could temporarily stop a node from processing blocks and transactions [1].
  • The attack sent an orphan transaction with thousands of missing parents, then inv messages repeating its ID 50,000 times; each message stalled the node for over a dozen seconds [1].
  • An automated LLM scan in Elias Rohrer's Project Loupe at Spiral found it in July; fixes are in versions 30.5, 31.3 and 32.1 [1][2].
  • Versions 29.0 to 29.5 are affected and will not be fixed because the 29.x series has reached end of life [1].

Bitcoin Core, the software most Bitcoin nodes run, disclosed on Nov. 20 a bug that let a single connected peer stop a node from processing blocks and transactions for stretches of time, and said the flaw was first found by an automated scan using a large language model [1].

The project rates the issue, CVE-2026-117348, as medium severity and "easily discoverable." Fixes ship in Bitcoin Core 30.5 and 31.3, released the same day, and in 32.1, released on Oct. 27 [1][2].

How the stall worked

Bitcoin Core keeps "orphan" transactions, whose parent transactions it has not yet seen, and asks peers that announce an orphan for the missing parents. Since version 29.0, when a peer announced a transaction already in the orphanage, the node built the list of the orphan's parents and checked each against its mempool and its filters of recently seen transactions [1].

A single inv message can carry up to 50,000 entries, and duplicate entries were not skipped. According to the advisory, an attacker could send a node an orphan with thousands of missing parents and then send inv messages repeating its ID 50,000 times. Each such message stalled the node for over a dozen seconds, during which it processed no messages from other peers, including new blocks [1].

The fix processes each transaction announced in an inv message only once [1]. The advisory describes a temporary stall, not a way to steal funds or change the ledger.

Found by an AI scan, then by a person

The advisory credits an automated LLM scan run as part of Elias Rohrer's Project Loupe at Spiral. Gregory Sanders validated the finding and brought it to the Bitcoin Core security team [1].

Project Loupe reported the issue on July 8. A researcher listed as Stutxo reported the same bug independently on Aug. 4, the day Sanders opened the fix, which was merged on Aug. 6. The fix was backported to the 31.x and 30.x branches on Nov. 17 before public disclosure on Nov. 20 [1].

The disclosure adds to a run of software flaws surfaced by AI tools this month; MLQ.ai has covered the wider debate in rushed patches, AI-found bugs and the wave of outages. Nothing in the advisory links this bug to those outages.

Who needs to upgrade

Affected versions are 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, so operators on it need to move to a newer release [1]. Bitcoin Core 31.3 is available from the project's release page [2].

Further sources

This article was produced by MLQ.ai's AI newsroom and checked against primary sources such as company filings, official releases and court documents. Reports from a single outlet are attributed. Editor: Peter Foy. How we work · Spotted an error? Tell us.

More like this