W3matchJoin

Creator Pulse, edition 1

Creator Pulse: Bitcoin Core's disclosed bugs require a configuration check

Edition 12 November 20264 min read3 sources

In one minute

Bitcoin Core disclosed details of three previously patched vulnerabilities on November 10. The issues have different triggers and consequences: a Tor permission error, a block-processing stall and a mining-template failure. Their disclosure does not establish a current network-wide attack.

The lead story

Three vulnerabilities, three different exposure paths

Bitcoin Core published the details of three vulnerabilities on November 10, 2026. The fixes were released in October 2025. That timeline matters: the fresh event is public disclosure, while the fixes were already available in supported releases.

Why now: The new disclosures give node operators and readers enough technical detail to distinguish the affected configurations. In CVE-2025-62860, inbound Tor peers could incorrectly receive permissions intended for trusted peers when a non-default whitelist covered the Tor proxy address. Those permissions relax some denial-of-service limits and privacy protections. Nodes without that whitelist setting were not affected.

The project says popular software bundles used the relevant configuration and that thousands of reachable mainnet nodes historically whitelisted incoming Tor connections. That is not a current count of vulnerable nodes, a count of all network nodes, or evidence of successful exploitation. Bitcoin Core rates the issue medium severity and lists fixes in versions 30.0, 29.2 and 28.3.

An angle worth explaining: A permission error is different from a broken Bitcoin consensus rule. The vulnerable node treated a remote peer as more trusted than intended because the address it saw was the local Tor daemon. The practical question is whether an operator's version and configuration matched that condition, not whether every Bitcoin transaction became invalid.

The disclosure also shows why software bundles matter. An operator may know they run Tor and a node without knowing which defaults a vendor selected. Checking the actual installed version and configuration, including vendor-provided packages, provides a more meaningful exposure assessment than counting downloads or assuming every reachable node shared the same settings.

What remains uncertain: The advisory does not establish the present number of affected installations or document successful attacks. Historical reachability is not a substitute for an up-to-date inventory of configurations.

A compact-block stall has a narrower trigger

CVE-2025-62859 concerns a block-processing delay in affected Bitcoin Core versions. A malicious peer that first announces a compact block could trigger a fallback request with a ten-minute timeout. The project says the delay could be repeated if an attacker controlled the victim's three high-bandwidth peers, or if the victim used blocksonly mode.

Why now: The details were disclosed on November 10, after fixes in Bitcoin Core 30.0 and 29.2 in October 2025. The defined conditions make this a useful case for explaining how a local node can be delayed without claiming that the entire network stopped.

An angle worth explaining: A compact block is a way for peers to communicate a block efficiently. When reconstruction fails, a node requests the full block. Here the handling of that fallback created a window in which an adversarial peer could delay the victim. The distinction between one victim's processing and network-wide consensus is essential when describing impact.

A mining-template failure came from mempool policy

CVE-2025-62861 affected Bitcoin Core versions 28.0 through 28.2 and 29.0 through 29.1. After a chain reorganization, an inconsistency in the mempool could prevent an affected mining node from creating valid block templates until restart. Bitcoin Core rates this issue high severity.

Why now: The November disclosure explains a failure mode that had been fixed in the releases listed by the project in October 2025. Its stated effect is on the affected node's template creation, rather than proof that a miner produced an invalid block accepted by the network.

An angle worth explaining: Mempool policy governs which unconfirmed transactions a node keeps and relays. Consensus rules determine whether blocks are valid. During a reorganization, transactions from disconnected blocks may be returned to the mempool. The bug allowed a policy operation to remove one transaction while leaving dependent transactions behind, making the assembled template fail its validity check. Restart restored a consistent mempool state according to the advisory.

The advisory does not quantify the mining power exposed when the bug was live. A current inventory of versions and operator reports would be needed to assess exposure.

Sources (3)
  1. CVE-2025-62860bitcoincore.org, Publication date not specified
  2. CVE-2025-62859bitcoincore.org, Publication date not specified
  3. CVE-2025-62861bitcoincore.org, Publication date not specified