News Bitcoin basics

Bitcoin Core fixes a node-stalling bug: which version should you check?

Versions 30.5 and 31.3, released on 20 November, fix a medium-severity vulnerability. Version 32.1 already contains the fix, while operators on the 29 series need to move to a supported branch.

Checked on 21 November 2026.

Navy server with an orange repair component linked to three pale blocks
Illustration: node software maintenance, without depicting a specific system.

The update concerns node software

Operators using Bitcoin Core to validate the Bitcoin network received two maintenance releases on Friday. The developers' announcement on 20 November 2026 presents a practical decision: identify the version actually running, then choose the appropriate upgrade path. Owning bitcoin does not, by itself, mean that someone runs this software.

According to the Bitcoin Core security advisory (Opens in a new tab), CVE-2026-117348 allows a network peer to temporarily delay a vulnerable node's processing of blocks and transactions. The issue concerns the receiving node's availability. The advisory does not describe stolen coins or report exploitation. Nor does it support a claim that the entire Bitcoin network stopped.

A node checks incoming information against network rules. If handling particular messages consumes too much processing time, legitimate information can also be left waiting. The distinction between an individual node and the wider network is explained in our guide to blockchains and validation rules.

Three branches, two new releases

The advisory lists the affected ranges as 29.0 through 29.5, 30.0 through 30.4, and 31.0 through 31.2. Versions 30.5 and 31.3 contain the fix. The 29 series has reached end of life and will not receive its own patch, Greg Sanders said on the developers' mailing list. Waiting for another maintenance release within that series is therefore not the route the team recommends.

Operators already running 32.1 have a different answer: its release on 27 October included the fix. The new announcement brings patched versions to two other maintained branches and publicly discloses the vulnerability. It is not a reason to move from 32.1 to 31.3 simply because the latter release appeared this week.

The underlying problem involved repeated processing of announcements about a transaction whose required parent transactions were still missing from the node. The fix prevents duplicate processing of the same transaction announcement within a message. Bitcoin Core credits an automated scan through Elias Rohrer's Project Loupe at Spiral with discovery, and Gregory Sanders with validating the finding and bringing it to the security team. This describes a discovery and remediation process, not evidence that every automated scan produces a valid finding.

What to check before replacing files

The 31.3 release notes instruct operators to stop the old software and wait for a complete shutdown before installing its replacement. They also say that upgrading from an end-of-life branch can take time if software data needs migration. Service operators should allow for that window rather than mistake planned maintenance downtime for the vulnerability being fixed.

It is useful to record the current version, installation-package source and service startup method beforehand. After restarting, checking the running version matters more than seeing a new file in the downloads folder. If a supplier packages the node inside another product, use that product's upgrade process rather than replacing components without checking compatibility.

For wallet or exchange users who do not manage their own node, the relevant software or service provider is the place to ask. The announcement does not require transferring funds or sharing a recovery phrase. The constructive result is a targeted fix, together with a clear distinction between branches that still receive maintenance and one that no longer does.

Correction and clarification

Found an error? Contact the editors

Share article Back to top