Blackmint
Blackmint Desk · Bitcoin · Nov 21, 2026

Bitcoin Core Patches Node-Stall Bug Found by an AI Code Scanner

Versions 30.5 and 31.3 fix CVE-2026-117348, a medium-severity flaw. The 29.x series stays exposed because it no longer gets fixes.

Orange circular bitcoin logo with a white B symbol
The bitcoin logo. Bitcoin Core is the most widely used software for running bitcoin nodes. Bitcoin logo via Wikimedia Commons (uploaded by Grayliptrot), Public domain.

Bitcoin Core released versions 30.5 and 31.3 on Friday to fix a medium-severity bug that let one peer freeze a node for more than a dozen seconds per message, according to the project's security advisory.

The flaw, CVE-2026-117348, affects versions 29.0 to 29.5, 30.0 to 30.4 and 31.0 to 31.2. Version 32.1, released Oct. 27, already had the fix. The 29.x series has reached end of life and will not be patched, the advisory said.

Repeated IDs, Repeated Work

A node is a computer that checks bitcoin transactions and blocks and passes them along. Sometimes it receives an orphan: a transaction spending coins from a parent the node hasn't seen yet. It holds the orphan and asks peers for the missing parents.

Peers announce transactions in batches of up to 50,000 entries, and Bitcoin Core did not skip duplicates. An attacker sending an orphan with thousands of missing parents, then its ID 50,000 times in one batch, forced the node to repeat the same lookups.

"Each such message stalls the node for over a dozen seconds," the advisory said. During that time the node handles nothing else, including new blocks. The fix makes it process each announced transaction once. CoinDesk reported that an exchange on an affected node might credit deposits late, and a miner could work from an outdated view of the chain.

Credit Goes to Project Loupe

The advisory credits an automated scan by a large language model, the type of AI behind chatbots, run through Elias Rohrer's Project Loupe at Spiral. Spiral is the open-source development unit of Jack Dorsey's Block, per CoinDesk. Developer Gregory Sanders checked it and wrote the fix. A second reporter, credited as Stutxo, flagged the same issue Aug. 4.

The advisory's timeline dates Loupe's report to July 8. The fix entered the main code Aug. 6 and reached the 30.x and 31.x branches Nov. 17. Both releases are on GitHub.

In our opinion: this bug sat in the code from version 29.0 until a machine read the fine print closely enough to spot it, and a human confirmed it. The exposure falls on anyone running 29.0 through 31.2, from hobby nodes to exchange back ends, and 29.x users get no patch at all. The scoreboard to watch is the advisory page: if Loupe's name keeps showing up in the credits, AI scanners are earning a regular seat at the security table.

Sources: Bitcoin Core: CVE-2026-117348 node stall through duplicate orphan announcements · Bitcoin Core: 31.3 released · Bitcoin Core: 30.5 released · GitHub: bitcoin/bitcoin releases · CoinDesk: Bitcoin nodes could be stalled by repeating one ID 50,000 times

Revisions

First published .

No revisions since publication.

We fix errors and say so. See every correction on the Blackmint corrections page.

Open in Blackmint →Blackmint · blackmint.markets · Not financial advice.