BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
Bitcoin

Bitcoin Core Patches Stall Bug Found by an AI Scan

Key Takeaways An automated LLM scan found the flaw first. A single message could stall nodes 12+ seconds. Fixed in 30.5, 31.3 and 32.1. Unsupported 29.x gets no patch at all. Bitcoin Core dev

AnonymousCryptoCompass newsroom
November 21, 2026
5 min read
NEWS
Bitcoin Core Patches Stall Bug Found by an AI Scan
CryptoCompass editorial visual for bitcoin coverage.

Key Takeaways

  • An automated LLM scan found the flaw first.
  • A single message could stall nodes 12+ seconds.
  • Fixed in 30.5, 31.3 and 32.1.
  • Unsupported 29.x gets no patch at all.

Bitcoin Core developers published the security advisory for CVE-2026-117348 on November 20, rating the bug medium severity and classing it as “easily discoverable”, a label that decides how quickly the public hears about a flaw.

How an AI Scan and a Second Researcher Found It

The first report arrived on July 8 from Project Loupe, Elias Rohrer’s research effort at Spiral. The flaw surfaced in an automated LLM scan, and Bitcoin Core contributor Gregory Sanders validated the finding before taking it to the project’s security team. On August 4, a researcher known as Stutxo reported the same issue independently.

Two unrelated parties finding one bug within four weeks is the risk the “easily discoverable” category is meant to address. Under Bitcoin Core’s disclosure policy, such bugs get a public advisory alongside the fixed releases, without the usual severity-based waiting period. By comparison, a high-severity mining-template bug disclosed earlier this month stayed under embargo for 396 days after its fix. Coindoo has covered why the project moved to the faster track.

What the Bug Did Inside a Node

An orphan transaction spends an output from an earlier transaction the node has not received yet. That alone doesn’t make it invalid. The node keeps it in a holding area, the orphanage, until the missing parents turn up.

Starting with version 29.0, when a peer announced an orphan by its wtxid, the node listed that orphan’s parents and checked each one against its mempool and its filters of recently seen transactions. Peers announce transactions in inv messages, which can carry up to 50,000 entries, and the software did not skip duplicates.

That gave an attacker an easy way to waste a node’s time. According to the advisory, the attacker could send an orphan with thousands of missing parents, then send inv messages repeating its wtxid 50,000 times. Every repeat would trigger the full parent check again. Each such message could stall the node for more than a dozen seconds, and in that window it would process nothing from other peers, blocks included. The advisory describes the stall as temporary and does not mention any exploitation.

Nothing in the advisory suggests the flaw let invalid transactions through validation or exposed wallet keys. It affected how fast a node could keep up, not what the node accepted.

Sanders opened the fix as pull request #35878 on August 4, and it was merged two days later. A patched node handles each announced transaction once per inv message, however many times the message repeats it. The 31.3 release notes list the change as “process unique tx INVs only.”

Who Got the Fix, and When

How the patch reached users depends on which branch they run:

32.x

Patched from launch

32.1, released October 27, shipped with the fix. 32.0 was tagged but never released.

31.x

Fixed November 20

31.0 to 31.2 are affected. Upgrade to 31.3.

30.x

Fixed November 20

30.0 to 30.4 are affected. Upgrade to 30.5.

29.x

No fix planned

29.0 to 29.5 are affected. The branch reached end of life on October 27.

Anyone on 32.x has run patched code since the branch’s first public release, weeks before the advisory went out. The 30.x and 31.x fixes were backported on November 17 and released alongside the advisory, so users of those branches learned about the flaw and received the patch at the same moment.

Bitcoin Core’s maintenance policy covers the three latest major versions, and branches past end of life generally don’t receive security fixes. The project recommends running the latest maintenance release of the most recent major version an operator can upgrade to.

Which Setups Feel a Stall First

While a node is stalled, it isn’t reading new blocks or transactions from its peers. The rest of the network carries on. Only that node’s view falls behind, and it catches up once processing resumes.

The exposure depends on what relies on that node. A merchant payment server, a wallet backend or a Lightning node that takes chain data from a single Bitcoin Core instance sees whatever delay that instance sees, so a payment can confirm on-chain before the service registers it. Operators who run several nodes or keep a fallback data source are better placed to ride out a stall on one of them.

READ MORE: Is Bitcoin Dead? Jack Mallers Points to Its History

Checking That a Node Is Patched and Keeping Up

A node that is running is not necessarily patched or in sync. After upgrading through the official release instructions, three checks confirm the fix is live and the node is current:

  1. Confirm the running version.bitcoin-cli getnetworkinfo returns a subversion field such as /Satoshi:31.3.0/. Query the live process, because a node that hasn’t restarted is still running the old binary.
  2. Confirm it has caught up. In bitcoin-cli getblockchaininfo, blocks should match headers once the node is in sync.
  3. Confirm dependent services see the same chain. Compare the node’s tip height against an independent source and against any payment, wallet or Lightning software that reads from it.

Operators still on 29.x won’t find a patched build to download. Closing this hole means moving to 30.5, 31.3 or 32.1.

The post Bitcoin Core Patches Stall Bug Found by an AI Scan appeared first on Coindoo.