Skip to content
PANTHER

Bitcoin Core Discloses Three Bugs. One Can Stop Block Building.

The newly published advisories concern older Bitcoin Core releases. Miners and node operators should check versions, Tor whitelist settings and peer exposure; fixes shipped in 2025.

By Panther@0xPnthr

3 min read

Conceptual illustration of a halted grayscale block-assembly machine with one square suspended above a gap, a small orange Bitcoin symbol and PANTHER JOURNAL #104.
Illustration: Panther, created with ChatGPT. Conceptual depiction of an affected mining node; not evidence of a current Bitcoin network outage.

Key points

  • Bitcoin Core disclosed three previously patched flaws on November 10, including a high-severity mining-template bug.
  • Tor whitelist exposure required a non-default configuration; compact-block stalling had specific peer conditions.
  • Check the actual deployed version and supported upgrade path. Historical fix versions are not current release recommendations.

A node can stay online while failing at the task a miner needs most: assembling a valid candidate block. Bitcoin Core’s newly published security advisories describe that failure in older releases, alongside two other flaws affecting block processing and Tor peer permissions.

The disclosures are dated November 10, 2026. The Block independently reported all three on November 11. The important timing distinction is that fixes shipped in October 2025. Operators checking exposure need the installed version and configuration, rather than the date of the headline.

The Bitcoin Core mining bug sits between the mempool and the next block

CVE-2025-62861 is rated high severity and affects versions 28.0–28.2 and 29.0–29.1. During a chain reorganization, transactions from disconnected blocks return to the mempool, the node’s pool of unconfirmed transactions.

The bug let TRUC “sibling eviction” policy run during that restoration. It could remove a transaction while leaving descendants that depended on its outputs. A miner using the resulting inconsistent mempool could then fail the validity check for its assembled block template.

The advisory says restarting restored a consistent mempool. That describes recovery from the state, not a replacement for installing a fixed release. It also explicitly distinguishes mempool policy from Bitcoin’s consensus rules: this was an implementation defect in handling transactions after a reorganization.

A Tor connection could inherit trust it never earned

The medium-severity CVE-2025-62860 advisory concerns the non-default -whitelist option. Incoming Tor peers could receive whitelist permissions when the Tor proxy’s address fell inside the configured trusted IP range.

Those permissions lift some denial-of-service limits and privacy protections intended for untrusted peers. Bitcoin Core says bundled software and client requirements led to thousands of reachable mainnet nodes whitelisting incoming Tor connections. That is the project’s reported observation, not a count Panther independently measured.

Nodes without that optional whitelist setting were never affected. The operational question is therefore specific: what did your node package or configuration mark as trusted? Using Tor alone does not establish exposure to this flaw.

The third flaw could delay block processing

CVE-2025-62859 is also rated medium severity. A malicious peer could exploit compact-block witness handling to push a victim into a fallback block request with a ten-minute timeout.

The advisory describes conditions in which the stall could be repeated indefinitely: an attacker controlling all three high-bandwidth peers, or a victim running in -blocksonly mode. The peer conditions matter; a ten-minute timeout is not evidence that every node was delayed.

Match the advisory to the machine you actually operate

Advisory Exposure to check Fixed releases named in the advisory
CVE-2025-62861 Mining node on 28.0–28.2 or 29.0–29.1 28.3, 29.2, 30.0
CVE-2025-62860 Older release plus a whitelist range covering the Tor proxy 28.3, 29.2, 30.0
CVE-2025-62859 Older compact-block processing; peer conditions affect repeatability 29.2, 30.0

Panther summary of the three primary advisories. These are historical fix thresholds, not a recommendation to install an obsolete branch.

Bitcoin Core’s official download page lists 32.1 as the latest version at this article’s check and provides checksum and signature-verification instructions. Operators using a node appliance or managed package should establish which Bitcoin Core build is actually running and follow the maintainer’s supported upgrade path.

For Bitcoin ($BTC) holders who do not operate infrastructure, these notices do not by themselves establish that wallet keys were stolen. The direct action belongs to node administrators, miners and the providers running their infrastructure. Panther’s earlier report on Bitcoin Core’s disclosure policy supplies the broader context; this release identifies the particular bugs and affected deployments.

Panther Takeaway

An online status indicator cannot tell you whether a mining node can build a valid template, whether peers have excessive permissions, or whether block processing can be stalled. Inventory the version, inspect the relevant settings and verify the supported upgrade. The disclosure is new; the fixes have been available for more than a year.

PANTHER JOURNAL #104

Responses

Links, wallet addresses and contact details are not allowed.

0/1000

No responses yet. Start the conversation.

Panther Journal — The intelligence brief

Stay ahead of the story.

Free. New investigations delivered when published. Unsubscribe anytime.

Launching something?

Work directly with Panther.

Start a project

More from Panther Journal