The Bitcoin Buzz

‹ All Posts

Bitcoin Core Reveals Three Patched Flaws, With a Clear Message for Node Operators

Bitcoin Core Reveals Three Patched Flaws, With a Clear Message for Node Operators

Bitcoin Core’s November 10 security disclosures were a reminder that Bitcoin’s resilience depends partly on the routine work of node and mining operators. The project published details of three older vulnerabilities after the final affected release series reached end of life. The issues had already been patched, and the disclosures did not describe a new breach of Bitcoin’s consensus rules or an emergency change to the network.

Bitcoin Optech summarized the three advisories in its November 13 newsletter: one high-severity vulnerability and two medium-severity vulnerabilities. Under Bitcoin Core’s disclosure policy, medium- and high-severity issues are publicly detailed two weeks after the last affected release reaches end of life. The 29.x series reached that point on October 27, clearing the way for the November disclosures.

The high-severity issue affected mining nodes running versions 28.0 through 29.1. During a chain reorganization, a bug in the handling of version-3, or TRUC, transactions could leave the mempool inconsistent. A miner using an affected node could then be unable to create a valid block template until restarting. Bitcoin Core says the flaw was fixed in version 30.0, released October 10, 2025, and then backported to the affected branches.

One medium-severity issue involved inbound Tor connections. On nodes using a non-default `-whitelist` configuration that included the local Tor daemon’s address range, incoming Tor peers could incorrectly receive trusted-peer permissions. Bitcoin Core says nodes without that configuration were never affected, but the setup had been used by thousands of reachable mainnet nodes. Fixes arrived in 30.0, 29.2, and 28.3.

The other medium-severity issue could let a peer that first announced a compact block stall a node’s processing of that block for up to 10 minutes, with repeated stalls possible under some conditions. It was a node-processing problem, not a way to create invalid Bitcoin or rewrite confirmed history.

The practical message is straightforward: operators still using an end-of-life release should move to a maintained Bitcoin Core version, using the project’s official download and verification guidance. The timing of the disclosures matters because it allowed the fixes to reach supported branches before technical detail became public. That sequence is an important part of responsible open-source security work.

Sources:
https://bitcoinops.org/en/newsletters/2026/11/13/
https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/
https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62861/
https://bitcoincore.org/en/lifecycle/

← Back to The Bitcoin Buzz