Bitcoin Core, the software most bitcoin nodes run, released versions 30.5 and 31.3 on Friday to fix a bug that let a hostile peer freeze a node for more than a dozen seconds at a time. The flaw, CVE-2026-117348, is rated Medium and was first found by an automated scan using a large language model, the advisory says.

Versions 29.0 to 29.5, 30.0 to 30.4 and 31.0 to 31.2 are affected. Version 32.1, released on 27 Oct, already carried the fix. The 29.x line has reached end of life and will not get one, so operators still on it need to move to a newer series.

How the stall worked

An orphan, in Bitcoin Core’s language, is a transaction whose parents the node has not yet seen. The node parks it and asks the peer that announced it for the missing parents.

Peers announce transactions in inv messages, short lists of transaction identifiers. Since version 29.0, when a peer announced a transaction that was sitting in the orphan pool, the node built the list of that orphan’s parents and checked each one against its mempool and its record of recently seen transactions.

One inv message can carry up to 50,000 entries, and duplicates were not skipped. An attacker could send an orphan with thousands of missing parents, then repeat its identifier 50,000 times in one message. Each such message stalled the node for over a dozen seconds, during which it processed nothing from other peers, including new blocks, according to the advisory.

The fix is simple: each transaction in an inv message is now processed once. The advisory does not report the bug being used against anyone.

The timeline, and my base case

Project Loupe, an LLM-based code scanner run by Elias Rohrer at Spiral, reported the bug on 8 Jul, and Gregory Sanders validated it and took it to the security team. A developer known as Stutxo reported it independently on 4 Aug. Sanders’ fix was merged on 6 Aug and shipped in 32.1 in October; the backports to the 31.x and 30.x branches were opened on 17 Nov and released on Friday with the disclosure.

That is the path set out in the fast-fix policy in October: bugs judged easily discoverable get point releases for every supported version and an advisory, rather than a year-long embargo. My base case then, which I called the short fuse, was that more fixes would arrive this way. Friday’s release is the second batch after three LLM-found bugs fixed in October, and it sits alongside the three older bugs disclosed on 10 Nov, which took the slow road.

The fuse was not that short this time: more than four months passed between the first report and the patched point releases. What would change my mind is a run of easily discoverable bugs that still wait for a major release before older versions are fixed. One case does not make that run, and the policy itself only dates from late October.

What to check

If your node runs 29.x, 30.0 to 30.4 or 31.0 to 31.2, upgrade to 30.5, 31.3 or 32.1. Packaged node distributions may take a few days to ship the new versions, so check your bundle’s release notes rather than assuming an automatic update.

This article is for information only and is not investment advice.