ec59b325-1

ConfirmedSecurity573 words3 min decode

Bitcoin Core Discloses Three Patched Node Vulnerabilities

Bitcoin Core disclosed three node vulnerabilities patched in October 2025, including a high-severity block template flaw; no exploits were reported and unsupported versions remain exposed.

Bitcoin Core discloses three security bugs affecting nodes
WitnessBitcoin Core discloses three security bugs affecting nodesThis_is_Engineering / pixabay

Outputs

  1. Bitcoin Core disclosed three vulnerabilities on November 10, 2026: one High and two Medium severity

  2. CVE-2025-62861 (High) blocked valid block template creation on versions 28.0–28.2 and 29.0–29.1 during reorgs with TRUC transactions

  3. All three flaws were patched in October 2025 releases; Bitcoin Core 30.0 shipped October 10, 2025 with fixes

  4. Bitcoin Core 29.x reached end of support October 27, 2026, closing the disclosure window

  5. No active exploits were reported for any of the three vulnerabilities

Bitcoin Core on November 10, 2026 published details of three security vulnerabilities affecting miners, node operators and Tor users, disclosing one High-severity and two Medium-severity flaws that were patched more than a year earlier in October 2025 releases. The project reported no active exploitation of any of the three bugs, and the residual risk is concentrated among operators still running software past its end-of-support date.

The disclosure window closed only after the last affected version line, Bitcoin Core 29.x, reached end of support on October 27, 2026. Bitcoin Core 30.0, which shipped on October 10, 2025 with all three fixes in place, has protected compliant operators for more than a year.

What did the high-severity bug do?

The headline issue, CVE-2025-62861, affected block template creation during chain reorganizations involving TRUC transactions. A block template is the draft block a miner assembles before attempting to mine it; a reorganization occurs when nodes discard recent blocks in favor of a competing chain. The combination could prevent miners from producing a valid block template at all — a direct hit to revenue-generating capacity for affected pools.

The flaw covered Bitcoin Core versions 28.0 through 28.2 and 29.0 through 29.1. It was reported on September 26, 2025, and backported into the October 2025 release series.

The two Medium-severity flaws carry narrower but operationally real consequences:

  • CVE-2025-62860 — Tor connection whitelisting. The optional -whitelist setting granted trusted permissions to inbound Tor peers, a misconfiguration Bitcoin Core says ran on thousands of reachable nodes. Only operators combining the non-default whitelisting configuration with Tor were exposed.
  • CVE-2025-62859 — compact block processing. A malicious peer could stall block processing for approximately 10 minutes. The issue was reported in April 2025.

What does this change for operators?

For the network at large, the practical impact approaches zero. Anyone on Bitcoin Core 30.0 or any patched October 2025 release has been covered since the fixes landed, and no exploits were reported during the entire disclosure embargo.

The exposure sits entirely with laggards. Miners on versions 28.0–28.2 or 29.0–29.1 remain open to the template bug, and those version lines now carry no vendor support at all — meaning no further patches will ever arrive for them. Node operators running the -whitelist flag alongside Tor face a different task: this is a configuration problem, not solely a version problem, and operators who copied the non-default setup should audit their configs even on current releases.

The scale is worth registering. Thousands of reachable nodes ran the whitelisting-plus-Tor combination — a meaningful fraction of the network's public infrastructure handed elevated trust to anonymous inbound peers for the duration of the embargo.

The disclosure pattern matters

The timeline illustrates Bitcoin Core's standing policy: fix quietly, backport across affected lines, and publish only when every vulnerable version has aged out of support. That approach minimizes the window in which disclosed details become a roadmap for attackers, at the cost of a long silence. Practitioners who assume embargoed bugs equal absent bugs should recalibrate accordingly.

The actionable deadline here has already passed: end of support for 29.x arrived October 27, 2026, so any operator still on 28.x or 29.x is now running unmaintained software with publicly documented vulnerabilities — an upgrade to 30.0 or later is the only remediation path.

via bitcoincore.org (Original)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,651 articles