The Ledger
Bitcoin Core discloses mining, Tor and block-processing flaws
Bitcoin Core disclosed three vulnerabilities on November 10, including a high-severity bug that could stop affected mining nodes from producing blocks until restart. The advisories also describe a Tor whitelist issue and a flaw that could stall block processing; fixes had been released in 2025.

A chain reorganization could leave affected Bitcoin Core mining nodes unable to produce blocks until they were restarted, while two other vulnerabilities affected Tor connections and block processing. Bitcoin Core published details of all three bugs on November 10, after fixes had been released in 2025.
Reorganization bug affected mining nodes
The high-severity issue, CVE-2025-62861, affected Bitcoin Core versions 28.0 to 28.2 and 29.0 to 29.1. The advisory says a reorganization could return transactions from disconnected blocks to the mempool, where an error in the software’s TRUC sibling-eviction handling could leave the transaction pool inconsistent.
Bitcoin Core’s account says the issue arose because sibling eviction could run while transactions were being restored, removing a transaction but leaving its descendants in the mempool. A miner’s block template could then fail its validity check, leaving a node that experienced the reorganization unable to produce blocks until it restarted and reloaded the mempool.
Niklas Goegge reported the flaw on September 26, 2025. Bitcoin Core’s timeline records fixes in versions 28.3, 29.2 and 30.0, released on October 17, October 14 and October 10, 2025, respectively.
Tor peers could inherit whitelist permissions
The medium-severity issue CVE-2025-62860 concerned the optional -whitelist setting. In Bitcoin Core, incoming Tor connections could be assigned permissions when the Tor daemon’s IP address matched a range configured as trusted. The advisory says those permissions lift denial-of-service limits and privacy protections.
Bitcoin Core says popular vendors bundled its software with a Tor daemon and configured a matching whitelist range, leading to thousands of reachable mainnet nodes whitelisting incoming Tor connections. Nodes that did not set the non-default option were not affected. Martin Zumsande and Antoine Poinsot reported the issue on September 12, 2025; fixes were released in versions 28.3, 29.2 and 30.0.
A peer could stall block processing
The third disclosure, medium-severity CVE-2025-62859, describes a compact-block handling flaw. After reconstructing a compact block, affected software cleared its download state before checking for witness malleation. If that check failed, the node requested the block from the same peer and waited through a 10-minute timeout, according to the advisory.
A malicious peer that announced the compact block first could use that behavior to stall block processing. The advisory says the disruption could be repeated indefinitely if the attacker controlled the victim’s three high-bandwidth peers or the victim ran with -blocksonly. Eugene Siegel reported the issue on April 28, 2025; Bitcoin Core lists fixes in versions 29.2 and 30.0, released in October 2025.
Sources
- Original source Bitcoin Core · page 1 bitcoincore.org
Other pages read
- Bitcoin Core · page 2 bitcoincore.org
- Bitcoin Core · page 3 bitcoincore.org