Bitcoin Core fixes medium-severity bug that could delay transaction processing

Bitcoin Core fixes medium-severity bug that could delay transaction processing
Bitcoin Core bug fixed

A newly disclosed software flaw in Bitcoin Core highlights how infrastructure weaknesses can ripple across crypto trading and mining operations. The issue could temporarily stop affected nodes from processing network messages, creating delays for exchange deposits and leaving miners working with outdated blockchain data.

Highlights

  • Bitcoin Core released fixes in versions 30.5 and 31.3 for a medium-severity bug exploited by repeating transaction IDs up to 50,000 times per batch.
  • The vulnerability allowed malicious actors to stall node operations, potentially causing exchanges to delay deposit credits and miners to waste computing power on outdated blockchain data.
  • Bitcoin Core's new policy, adopted Oct. 22, prioritizes rapid public fixes for easily discoverable flaws, citing AI-driven tools like Loupe as drivers of quicker vulnerability identification.

Fixes released across maintained versions

As reported by CoinDesk, Bitcoin Core released fixes on Friday in versions 30.5 and 31.3 for a medium-severity vulnerability that was flagged by Loupe, an open-source scanning tool from Block's Spiral unit that uses AI agents to examine bitcoin code. The flaw allowed a node to be stalled by repeating a transaction identifier up to 50,000 times in a single announcement batch.

The bug affected how Bitcoin Core handled orphan transactions, which are payments spending coins from an earlier transaction the node has not yet seen. Since version 29.0, when another node announces one of these orphans, the software builds a list of missing parent transactions and checks its records before deciding what to request.

Nodes can announce transactions in batches of up to 50,000 entries, but the software did not skip repeated entries. An attacker could first send an orphan transaction with thousands of missing parents, then repeat its ID 50,000 times, forcing the receiving node to carry out the same expensive checks again and again. Bitcoin Core said each such message stalls the node for more than a dozen seconds, and further messages could extend the disruption.

Operational risks for exchanges and miners

The practical effects reach beyond a technical nuisance for node operators. An exchange relying on an affected node could face delays in crediting customer deposits, while a miner could waste computing power on an outdated view of the blockchain because the node is not processing fresh messages, including new blocks.

Bitcoin Core rated the issue as both medium severity and easily discoverable. Under the security policy adopted on Oct. 22, flaws considered easily discoverable receive fixes across maintained versions as quickly as possible, together with a public advisory.

The released fix ensures each transaction announced in a batch is processed only once. The policy also reflects concern among developers that AI tools are making some vulnerabilities cheaper to rediscover, reducing the value of keeping fixes private for extended periods.

We have also looked at high-cost miners facing added pressure as bitcoin’s price correction widened the gap to estimated production costs, JPMorgan said.

This material may contain third-party opinions, none of the data and information on this webpage constitutes investment advice according to our Disclaimer. While we adhere to strict Editorial Integrity, this post may contain references to products from our partners.