Bitcoin Core Patches Bug Found by AI That Could Stall Nodes
A single transaction ID repeated 50,000 times could temporarily stall a Bitcoin Core node. An AI scan via Spiral's Project Loupe found the bug; versions 30.5 and 31.3 fix it, while the retired 29.x branch gets no patch.
Feed a Bitcoin Core node one transaction ID repeated 50,000 times and it could temporarily stop processing network messages. Bitcoin Core disclosed that medium-severity bug on Friday, Nov. 20, and shipped fixes in versions 30.5 and 31.3.
The flaw is tracked as CVE-2026-117348. According to the advisory, it was found by an automated AI scan run through Elias Rohrer's Project Loupe at Spiral, Block's open-source development unit. Loupe is an open-source scanner that uses AI agents to examine bitcoin code.
What the bug does
It involves orphan transactions: payments that spend coins from an earlier transaction the node has not yet seen. When one arrives, the node goes looking for the missing pieces. Since version 29.0, Bitcoin Core builds a list when another node announces an orphan.
The stall is temporary, but attackers could stretch it by sending additional messages. The possible fallout: delayed exchange deposits, or miners working with outdated blockchain information.
The fix is simple in concept. Each transaction announced in a batch is now processed only once.
Severity and policy
Core developers rated the bug "medium severity" and "easily discoverable." That second label matters. Under the security policy Bitcoin Core adopted on Oct. 22, easily discoverable flaws get fixes across maintained versions as soon as possible, with a public advisory published alongside the releases. This disclosure follows that playbook: patches and advisory landed together.
One catch for stragglers. The retired 29.x branch will not get a fix, so anyone still running it needs to move to a maintained release.
Why traders and node operators should care
A medium rating fits a temporary stall. Still, the downstream scenarios are the kind that touch PnL at the edges: exchange deposit lag and miners on stale data are operational headaches worth pricing in if you run infrastructure.
The bigger signal is where the bug came from. An AI agent scan surfaced an issue developers themselves call easily discoverable, and that cuts both ways. Defenders get a new tool. So does anyone else pointing automated scanners at the same code.
It also lands shortly after Bitcoin Core's Nov. 10 disclosure of other bugs, including a Tor whitelist flaw, so this is the project's second batch of advisories this month.
Node operators on 30.x or 31.x should upgrade to 30.5 or 31.3 respectively.






