Bitcoin
Bitcoin Core 30.5 fixes a temporary stall in block processing
Bitcoin Core released version 30.5 on November 20. It fixes a node software flaw that could delay the processing of blocks and transactions. The 31 series gets the same fix in version 31.3, while the 29 series has reached end of life.

Node software processes each distinct announcement once
A Bitcoin node receives notices of new transactions from its peers, then decides which ones it needs to retrieve and verify. Some transactions arrive before those they depend on. A node can keep them temporarily while waiting for the information it needs. In its November 20 advisory, the Bitcoin Core project says repeated announcements could monopolize that processing. An affected node could temporarily stop processing messages from its other peers, including new blocks.
The fix changes how the software handles redundant announcements. The advisory says each announced transaction is now processed once within a single inventory message. The project rates the issue, identified as CVE-2026-117348, medium severity. The effect described in the advisory is an interruption in a node’s message processing. It therefore affects the availability of the node software as it handles continuing network traffic.
Three branches have a patched release
The advisory lists versions 29.0 through 29.5, 30.0 through 30.4, and 31.0 through 31.2 as affected. The correction had already been included in Bitcoin Core 32.1, released on October 27. On November 20 the project made it available in two older branches through versions 30.5 and 31.3. The 30.5 release notes also mention changes to automated testing infrastructure and updated translations.
The 29 series reached end of life on October 27, according to the project’s schedule. Bitcoin Core says it will not receive the fix. For operators, that distinction affects the scope of an upgrade. Users of the 30 and 31 series have maintenance releases within their branches, while getting a patched version requires an operator on the 29 series to move to a newer branch.
The security advisory was published alongside the updates
The project’s timeline dates the first report to July 8 and a separate report to August 4. The correction was merged into the development branch on August 6 and backported to the 30 and 31 branches on November 17. The project disclosed the issue on November 20, the day it released both maintenance updates.
The project’s maintenance schedule says it supports the three most recent major versions. Maintenance releases let the project distribute fixes to multiple branches during that period. The November 20 announcement shows how this works. For each affected branch it identifies the versions that operators still need to update and the versions in which the project has shipped the correction.
