News

Bitcoin Core fixes Tor trust and mining bugs

Bitcoin Core disclosed three already-patched flaws affecting compact block handling, Tor peer permissions and block template creation. No exploitation has been reported.

4 min readBitcoin Core
Bitcoin Core fixes Tor trust and mining bugs

What happened

On 10 November 2026, Bitcoin Core published three security advisories for flaws fixed in releases made during October 2025. One could repeatedly delay block processing. Another could give strangers connecting over Tor permissions meant for trusted peers. The third could leave a mining node unable to create a valid block template until it restarted.

The project waited to disclose the details until the last vulnerable release branch reached end of life on 27 October 2026. Bitcoin Core says the fixes are in 28.3, 29.2 and 30.0. It reports no known exploitation.

The highest-rated bug, CVE-2025-62861, affected Bitcoin Core 28.0 through 28.2 and 29.0 through 29.1. During a chain reorganisation, a transaction eviction rule could leave the mempool inconsistent. A miner that then asked the node for a block template could receive one that the same node rejected. Restarting cleared the condition, but an attacker able to trigger the pattern again could keep interrupting mining.

What it changes

The Tor permission bug matters to operators who used the non-default -whitelist setting. Bitcoin Core checked the proxy address instead of the hidden service peer's address. If the proxy address fell inside a trusted range, every inbound Tor peer could inherit permissions intended for a known peer.

Bitcoin Core says popular node bundles placed the Tor proxy in a whitelisted private range, so thousands of reachable nodes were affected. Those extra permissions could allow a stranger to bypass normal protections, including some disconnect and relay limits. Nodes that never enabled -whitelist, and connections that did not arrive through the affected proxy setup, were not exposed by this flaw.

The third bug, CVE-2025-62859, used witness malleation against compact block reconstruction. A malicious peer could make a node spend up to ten minutes trying to obtain the right transaction before processing the block. The attacker could repeat the delay when it controlled three high-bandwidth peers, or against a node using -blocksonly with fewer connections.

Operators running any affected release should move to a maintained Bitcoin Core version from the official download site. Version 29.2 contains the fixes, but the 29.x branch is now out of support. A maintained branch is needed for later security updates as well.

What it does not change

The advisories describe availability and peer-permission failures. They do not describe a way to steal private keys, create bitcoin, change the supply limit or make an invalid transaction valid.

The mining bug did not alter consensus. The affected node rejected its own bad template before mining it. The immediate harm was an interruption in block production for that operator, not acceptance of an invalid block by the network.

The Tor flaw also did not make every Tor connection trusted. It required an operator or bundle to combine inbound Tor with a matching -whitelist rule. Bitcoin Core's estimate of thousands of affected nodes comes from public reachability measurements and common bundle settings, not a count of confirmed compromises.

These disclosures are new, but the software fixes are not. A node already running a maintained release has the patches. The three flaws are also separate from the memory and undo-file bugs disclosed on 28 October.

Context

Three independent newsrooms checked the advisories. CoinDesk focused on the scope of the Tor permission error. The Block compared the affected versions and the high-severity mining failure. Decrypt explained how the block-template failure could stall an operator without breaking consensus. Unchained also distinguished these flaws from the October 28 disclosures.

The reports agree on the mechanisms, fixed versions and lack of known exploitation. None establishes that an attacker used any of the three bugs in the wild. The delayed publication follows Bitcoin Core's existing practice of giving operators time to upgrade before technical details become public.

Newsletter

Bitcoin, without the noise

What happened in Bitcoin, what it actually changes, and the sources so you can check us. One issue at a time, straight to your inbox.

  • One email per issue, never a drip campaign
  • No tracking pixels and no shared addresses
  • Unsubscribe from any issue in one click

Get the next issue

One email per issue, no tracking pixels, and unsubscribe from any of them. We do not share your address. Privacy policy