Key points
- Bitcoin Core 30.5 and 31.3 include the fix; 32.1 already had it.
- The issue can slow transaction relay on affected nodes. The disclosure does not establish a network-wide outage or loss of coins.
- 29.x is outside maintenance. Operators should plan a move to a supported release.
A Bitcoin node can still be online while it falls behind on the work the rest of the network is sending it. The Bitcoin Core node stall fix addresses that kind of slowdown. The Nov. 20 releases fix a flaw that can delay transaction relay by tying up an affected node’s handling of network messages. The first thing to check is the version the node is actually running.
PANTHER JOURNAL #135 · SECURITY
Maintainers published Bitcoin Core 30.5 and 31.3 on Nov. 20, 2026. The current 32.1 release already includes the same fix. The project rates the flaw, CVE-2026-117348, medium severity. Independent reporting by freenode confirms the patched versions and the gap for operators still on 29.x. This is a separate disclosure from the three Bitcoin Core bugs Panther covered on Nov. 11.
Which versions include the Bitcoin Core node stall fix?
- 30.x: Move to 30.5 if you need to stay on that branch.
- 31.x: Move to 31.3 if you need to stay on that branch.
- 32.x: Run 32.1 for this fix.
- 29.x or older: Plan a move to a supported branch. The project’s maintenance policy lists 29.x as out of support since Oct. 27. A wait for another 29.x maintenance update won’t deliver this fix.
A backport takes a fix that already exists in a newer release and brings it to an older branch. Here, that lets operators on 30.x or 31.x address the disclosed issue without changing major versions. Teams that stayed on 29.x for compatibility need to check what depends on it, including wallet software, plug-ins or package managers, and plan the move using the release notes.
Where readers might notice the slowdown
A node can verify transactions and pass them to its peers. If the node a service uses is slow to relay new transactions, that service can take longer to broadcast a payment or show activity it normally sees promptly. The advisory concerns node responsiveness. It does not establish a network-wide outage, a change to Bitcoin’s ($BTC) rules, or any loss of coins. A slow transaction on its own also tells you nothing about whether a node hit this particular bug.
One useful distinction: a service may show a transaction as pending before the network confirms it. When something looks stuck, note the transaction ID and compare what your own software sees with another source you trust. An explorer can tell you what its node sees; it cannot tell you whether your node has this patch. Check the installed software separately before drawing that conclusion.
Verify the upgrade from both ends
Use the project’s download and signature verification instructions and the release notes for your platform. If you run a node through an appliance or a hosted service, find out which Core version the provider actually deploys. If you maintain several nodes, record which version each one runs and update them in stages so you can spot any compatibility problems. After an update, check the running process and confirm it has caught up; a newly downloaded installer or a green status light can’t tell you the version of the process handling traffic.
For a business that relies on one node for payment alerts, the restart itself also matters. The release notes advise letting an older process shut down completely before installing the update. Schedule that pause, and check that the service using the node sees current blocks again before treating it as back in service. For a managed node, ask for the running version and an upgrade window rather than relying on a generic statement that the provider has applied its latest updates.
Panther Takeaway
Start with the version you run. On 30.x or 31.x, the Nov. 20 releases give you a patch on your current branch. On 29.x, the durable fix is to leave an unsupported branch behind.
Responses
No responses yet. Start the conversation.
Panther Journal — The intelligence brief
Stay ahead of the story.
Free. New investigations delivered when published. Unsubscribe anytime.






