0bbfb389-d

ConfirmedSecurity928 words5 min decode

Bitcoin Core Discloses Three Fixed Security Vulnerabilities

Bitcoin Core disclosed three patched flaws on Nov. 10, 2026: a high-severity mining failure, a repeatable block-processing delay and an optional-whitelist Tor permission flaw.

Bitcoin Core Discloses Three Patched Bugs, Including Mining Flaw
WitnessBitcoin Core Discloses Three Patched Bugs, Including Mining Flawtimwesterhoff / pixabay

Outputs

  1. One high-severity and two medium-severity flaws were disclosed on Nov. 10, 2026.

  2. The mining flaw, CVE-2025-62861, affected Bitcoin Core 28.0–28.2 and 29.0–29.1.

  3. Bitcoin Core 30.0 shipped all three fixes on Oct. 10, 2025; 29.2 did so on Oct. 14, and 28.3 fixed the mining flaw.

  4. The block-processing flaw could delay an affected node for up to 10 minutes and repeat indefinitely in some configurations.

  5. Niklas Goegge reported the mining vulnerability on Sept. 26, 2025; developers later reported no evidence of exploitation.

Bitcoin Core developers disclosed three previously patched vulnerabilities on Nov. 10, 2026, including one high-severity flaw that could stop an affected miner’s node from building new BTC blocks until restart, according to the project’s security advisories.

Bitcoin Core 28.0–28.2 and 29.0–29.1 carried the mining flaw, CVE-2025-62861. Two other bugs carried medium severity: CVE-2025-62859 for block processing and CVE-2025-62860 for Tor permissions. Fixes shipped in October 2025. According to Decrypt, developers reported no evidence of exploitation.

Bitcoin Core is the reference software used by the majority of Bitcoin nodes. Its severity-based policy explains the yearlong gap between patches and advisories.

Disclosure timing is changing. In an Oct. 22, 2026 message to the Bitcoin Development Mailing List, developer Antoine Poinsot argued that an embargo on easily found flaws “achieves little but it delays the availability of a fixed release.” He pointed to large language models reducing the effort needed to find flaws, including previously concealed fixes.

The policy pull request went in on Oct. 16 and merged on Oct. 22. It created an “easily discoverable” classification, which can include vulnerabilities found through a simple AI prompt.

What broke the miner’s block template?

The high-severity issue sat in block-template creation. It involved version 3 transactions, known as TRUC, and BIP-431 restrictions on mempool admission and relay. BIP-431 permits one unconfirmed ancestor and one unconfirmed descendant; valid blocks may contain arrangements outside those policy limits. They were central to the sibling-eviction behavior.

A chain reorganization disconnects accepted blocks when the network adopts an alternative chain. Their transactions return to the mempool for reuse. Bitcoin Core restores them with bypass_limits=true, relaxing normal mempool limits and transaction-topology restrictions.

Bitcoin Core 28.0 introduced TRUC sibling eviction. Under replace-by-fee rules, a sufficiently paid new child could remove an existing child. The faulty branch continued while limits were bypassed, allowing a restored transaction to disappear while other transactions still spent its unavailable outputs.

That left the mempool inconsistent and failed the block-template validity check. The miner could not produce blocks through the affected node until restart. That interrupted the work through which the miner earns block rewards.

What could the other two flaws do?

CVE-2025-62859 allowed a malicious peer to stall block processing with manipulated transaction witness data. The scenario involved the peer announcing a compact block. An affected node could wait up to 10 minutes before processing it.

Specific configurations made the attack repeatable indefinitely. A malicious peer could keep delaying a susceptible node rather than cause one interruption. This flaw hit incoming block processing; the mining bug hit creation of a new template after reorganization.

CVE-2025-62860 wrongly granted whitelist permissions to inbound Tor connections. Those permissions lifted protections intended to limit denial-of-service and privacy risks. Exposure depended on the optional whitelist configuration.

U.Today reported that thousands of reachable Bitcoin mainnet nodes had been granting such permissions. Operators therefore needed to review configuration as well as software version. The software applied controls meant for selected peers to inbound Tor connections incorrectly.

Both flaws ranked medium severity in a framework running from low to critical; the mining flaw ranked higher.

When did the fixes and advisories arrive?

Security researcher Niklas Goegge first reported the mining vulnerability on Sept. 26, 2025. Developers integrated repairs and shipped them. Public disclosure on Nov. 10, 2026 then exposed details addressed in the previous year.

Bitcoin Core 30.0, released on Oct. 10, 2025, and Bitcoin Core 29.2, released on Oct. 14, 2025, included fixes for all three vulnerabilities. Bitcoin Core 28.3 separately included the mining-vulnerability fix.

The report, patch releases and public disclosure occurred separately. Restarting restored block-template creation after the inconsistent mempool state, while installing a patched release addressed the underlying flaw.

What changed in the disclosure policy?

Bitcoin Core’s policy generally delays disclosure of medium- and high-severity vulnerabilities until at least two weeks after the last affected release reaches end of life. The embargo typically lasts about a year after the initial fix.

Critical issues receive separate handling. That category covers protocol-level coin theft, unauthorized coin creation and permanent network-wide chain splits. The disclosed batch remained within the high and medium tiers.

For easily discoverable vulnerabilities, developers will backport fixes to every actively maintained major version. They will publish security advisories alongside those patched releases. Vulnerabilities outside that classification retain severity-based disclosure timelines.

Poinsot acknowledged that faster security releases could reduce testing time in development branches. He argued straightforward, easily verified repairs can justify accelerated delivery.

What should node operators do now?

Miners should confirm the release used by the node supplying block templates and install a version containing the TRUC repair. Bitcoin Core 28.3 addresses the mining flaw; 29.2 and 30.0 carry all three fixes.

Tor operators should audit the optional whitelist and how inbound Tor connections are handled. Other operators should review configurations that could permit a malicious peer to repeat the compact-block delay. Bitcoin Core urges operators to run the latest release.

For an affected miner, a restart offers immediate recovery but does not close the route. For the network, version checks alone no longer capture the exposure; configuration review now belongs in the same checklist.

The next checkpoint is the next backport across actively maintained branches. Under the revised policy, advisories for easily discoverable flaws will arrive with the patched release rather than after the usual embargo.

via bitcoinfoundation.org (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,581 articles