BTC—ETH—SOL—XRP—BNB—ADA—DOGE—TRX—LINK—AVAX—DOT—LTC—
Live

Bitcoin Core patches a node-stalling bug an AI scanner found

Bitcoin Core shipped versions 30.5 and 31.3 on November 20 to patch a denial-of-service bug that let one peer stall a node for seconds at a time. An AI-driven scanner from Block's Spiral unit found the flaw, which had sat in the code since version 29.0.

By Zain

Published · 5 min read

Bitcoin Core developers released two updates on November 20, 2026, to fix a bug that let one peer freeze a node for seconds at a time. An open-source scanner that runs AI agents found it first.

Developers published a security advisory the same day. The fix ships in Bitcoin Core versions 30.5 and 31.3. The flaw is tracked as CVE-2026-117348 and rated medium severity, and no one has reported it being used in an attack so far.

What the bug actually did

Every Bitcoin node keeps a short list of orphan transactions. These are payments whose parent transaction has not arrived yet, so they wait outside the ordered mempool until the rest shows up. The node holds them and keeps looking for the missing parents. That lookup costs work.

Here is where it broke. An attacker could announce the same transaction ID 50,000 times inside one message. Older code did not skip the duplicates, so the node ran the same expensive check over and over. Each message tied it up for more than a dozen seconds, the advisory said. During that pause it ignored everything else, new blocks included.

Think of a bouncer forced to scan one fake ID 50,000 times while the queue backs up behind him. The stall was not permanent. A single hit would barely register. Strung together, though, repeated messages could keep a node off the network long enough to matter.

Both effects were small but real. An exchange could credit a customer deposit late. A miner could build on stale blockchain data for a short window. No funds were at risk. The damage was to timing and reliability, not to anyone's coins.

Denial-of-service bugs are a recurring theme in Bitcoin Core advisories. The software has patched several over the years that let peers slow or stall message processing. None of them move money, which is the point of the design. The attacker wastes a node's time, not its balance.

How an AI scanner caught it

Loupe surfaced the bug. The open-source tool comes from Spiral, the Bitcoin-focused unit inside Block, the payments company run by Jack Dorsey. Loupe sends AI agents through Bitcoin's codebase to hunt for weak spots a human reviewer might pass over.

Bitcoin Core credited the find to an automated scan run through Elias Rohrer's Project Loupe. The flawed orphan handling had been in the code since version 29.0. It sat there for months before the scan flagged it. Months, unnoticed.

AI code review is new to Bitcoin, and one medium bug does not prove the method. What it does show is that an automated scan can pull a real finding out of software many people have already read line by line. That is the quieter headline here.

Spiral has backed Bitcoin development for years, funding engineers and open-source work. Pointing machine agents at the codebase is a newer step. The appeal is coverage. A scanner can read every path through the software without tiring, which is exactly the kind of tedious check where human attention drifts.

Part of a busier disclosure season

This is not Bitcoin Core's only recent notice. On November 10 the project disclosed three older flaws that had already been patched back in October 2025, including a high-severity bug that could stop miners from building valid blocks, according to The Block. Those fixes were more than a year old by the time they were made public.

Some of the pace is by design. In October the project adopted a security policy that calls for fixing easily discoverable bugs quickly and disclosing them on a schedule. The new orphan bug fits that shape. Found by a scan, rated medium, patched, then announced.

Who should update, and when

The fix itself is simple. Node operators should move to Bitcoin Core 30.5 or 31.3. Because the vulnerable behavior reaches back to version 29.0, anyone on an older build should check which version they run and upgrade.

One group gets no patch. The 29.x series has passed its end of support, and developers will not fix it there. Users still on that line need to move to a supported release, not wait for a backport that is not coming.

For ordinary holders, there is nothing to do. The people who run full nodes, exchanges and mining pools carry the risk, and most professional operators update fast. How many nodes still run the old code is not known.

What to watch

The next signal is how quickly node operators move. Bitcoin Core can see the version numbers that reachable nodes report, so the share still running affected builds will show up over the coming weeks. A slow upgrade curve would say more than the bug did.

There is a trust angle too. Every clean disclosure, patched before it bites, is evidence the review process works. A missed bug that gets exploited would be the opposite. So far the record on this one looks like the system doing its job.

Watch the tooling too. Loupe is open source, and its early win will push other teams to point similar scanners at Bitcoin and at other chains. Mining security has already had a rough stretch, after an attacker redirected client hashrate at Luxor weeks earlier. If automated review keeps producing valid findings, disclosure notices like this one could turn routine.

Frequently asked

What is CVE-2026-117348?

CVE-2026-117348 is a medium-severity denial-of-service bug in Bitcoin Core. A single peer could stall a node for more than a dozen seconds by announcing the same transaction ID 50,000 times. Bitcoin Core fixed it in versions 30.5 and 31.3, released on November 20, 2026. There is no public sign it was ever used in an attack.

Which Bitcoin Core versions are affected, and which are safe?

The flaw reached back to version 29.0, when the orphan-transaction handling was added. Nodes running 30.5 or 31.3 and later carry the fix. The 29.x series has passed its end of support and will not be patched, so operators still on that line should upgrade to a supported release rather than wait.

How did an AI tool find a Bitcoin bug?

The bug came from Loupe, an open-source scanner from Spiral, the Bitcoin unit inside Jack Dorsey's Block. Loupe runs AI agents through Bitcoin's code to flag weak points. Bitcoin Core credited the find to a scan through Elias Rohrer's Project Loupe. It is an early result, but it points to more automated review ahead.

Sources, and what is behind them

  1. Bitcoin Core security advisories (CVE-2026-117348), Bitcoin Core (November 20, 2026)Documentation
  2. Bitcoin nodes could be stalled by repeating one ID 50,000 times. AI found the bug, CoinDesk (November 21, 2026)Press report
  3. Bitcoin Core discloses three patched security flaws, including high-severity mining bug, The Block (November 11, 2026)Press report