BitcoinBTC, coin
DisputedSecurityOfficial source

Bitcoin Core discloses three patched flaws, including one that could stop miners building new blocks

Bitcoin Core published advisories for three vulnerabilities patched in October 2025, including a high-severity bug that could leave mining nodes unable to build blocks after a reorganization.

Read this event in 中文(中国), 日本語, русский, Türkçe

Why it matters

Decrypt, Bankless and Brave New Coin reported the flaws enabled denial-of-service and privacy problems rather than coin theft or forgery, and no exploitation was reported. Crypto News reported that about 9% of reachable nodes still ran vulnerable versions when the details went public, leaving those operators exposed until they upgraded.

Where the sources disagree

Which releases contain the fixes

Fixes in 30.0 (Oct. 10, 2025) and 29.2 (Oct. 14, 2025)

Unchained

CVE-2025-62861 fix in 30.0, 29.2 and 28.3

Crypto News (CryptoNews.net), Bitcoin Insider, U.Today, Unchained, Decrypt, CryptoPotato, Bankless, Bitcoin.com News

Unchained reported all three fixes shipped in Bitcoin Core 30.0 on Oct. 10, 2025 and in 29.2 four days later, while Crypto News reported the CVE-2025-62861 correction appeared in 30.0, 29.2 and 28.3.

Whether the bugs were exploited

No exploitation reported

Decrypt, Bankless

Advisories do not state whether any bug was exploited

Unchained

Decrypt and Bankless reported that no exploitation occurred, while Unchained wrote that the advisories do not say whether any bug was exploited.

Duration of the CVE-2025-62859 processing delay

Up to 10 minutes, repeatably in certain setups

U.Today, Bankless

Could continue indefinitely under particular conditions

Crypto News (CryptoNews.net)

U.Today and Bankless reported a delay of up to 10 minutes, while Crypto News reported the interference could continue indefinitely under particular network conditions.

Key facts

Bitcoin Core published three security advisories on Nov. 10, 2026, describing bugs that were patched more than a year earlier.

Reported by Bitcoin Insider

CVE-2025-62861, rated high severity, involved TRUC (version 3) transactions and sibling eviction, and after a chain reorganization could leave a node running versions 28.0 to 28.2 or 29.0 to 29.1 unable to build block templates until it was restarted.

Disputed figureReported by Bitcoin Insider

Niklas Goegge reported the mining bug on Sept. 26, 2025, and Greg Sanders' correction merged on Oct. 2 and shipped in Bitcoin Core 30.0, 29.2 and 28.3 during October 2025, per U.Today and Crypto News.

Disputed figureReported by U.Today

CVE-2025-62860 let inbound Tor connections inherit trusted-peer permissions when operators included their Tor daemon's address in the -whitelist setting, which Bitcoin Core said affected thousands of reachable mainnet nodes.

Disputed figureReported by Bankless

Disclosure came after the 29.x release line reached end of life on Oct. 27, 2026, because Core's policy holds Medium and High disclosures until two weeks after that point, per Unchained and Bankless.

Reported by Bitcoin Insider

Crypto News reported that approximately 9% of reachable nodes still advertised vulnerable versions around the disclosure date.

9 %Reported by Crypto News (CryptoNews.net)

No exploitation was reported and none of the three flaws enabled coin theft, inflation or a chain split, according to Decrypt and Bankless; Unchained noted the advisories do not state whether any bug was exploited.

Disputed figureReported by Unchained

What happened

Bitcoin Core published three security advisories on Nov. 10, 2026, describing vulnerabilities that were patched in October 2025 releases, and Decrypt, Bankless and Brave New Coin reported that no exploitation was recorded. The high-severity bug, CVE-2025-62861, involved TRUC (version 3) transactions and the 'sibling eviction' rule; after a chain reorganization a node's mempool could hold child transactions whose parent had been wrongly evicted, leaving the node unable to build block templates until it was restarted. U.Today and Crypto News reported that security researcher Niklas Goegge reported that bug on Sept. 26, 2025, and Crypto News reported that Greg Sanders' fix merged on Oct. 2 and shipped in Bitcoin Core 30.0, 29.2 and 28.3. A second bug, CVE-2025-62859, let a maliciously crafted compact block delay block processing by up to 10 minutes, repeatably in certain setups, per U.Today, Bankless and Crypto News. The third, CVE-2025-62860, let inbound Tor connections inherit trusted-peer permissions when operators whitelisted their own Tor daemon's address, which Bitcoin Core said affected thousands of reachable mainnet nodes. Unchained and Bankless reported that disclosure waited until two weeks after the 29.x release line ended support on Oct. 27, and Crypto News reported that about 9% of reachable nodes still advertised vulnerable versions around the disclosure date.

How the story developed

  1. Update

    29.x release line reached end of life

    Unchained, Bankless and Bitcoin Insider reported support for version 29 ended on Oct. 27, which started the two-week disclosure window under Core's policy.

    Bitcoin Insider

  2. Official statement

    Bitcoin Core published the three advisories

    The advisories on bitcoincore.org covered CVE-2025-62861, CVE-2025-62860 and CVE-2025-62859.

    Bitcoin Insider

  3. First report

    First report by Bitcoin Insider

    Bitcoin Core Discloses Three Patched Flaws, Including One That Can Stop a Node From Building Blocks

    Bitcoin Insider

  4. Resolution

    Fixes shipped in Bitcoin Core 30.0 and 29.2

    Unchained dated 30.0 to Oct. 10, 2025 and 29.2 to four days later; Bitcoin Insider and Bankless noted the fixes shipped in October 2025 releases, and Crypto News also listed 28.3 for CVE-2025-62861.

    Bitcoin Insider

  5. Update

    First media coverage of the disclosure

    Bitcoin Insider reported the advisories on the morning of Nov. 11, followed the same day by U.Today, Unchained, Decrypt, CryptoPotato and Bankless.

    Bitcoin Insider

  6. Update

    Niklas Goegge reported the mining bug to Bitcoin Core

    U.Today and Crypto News dated the report to Sept. 26, 2025; Crypto News reported Greg Sanders' fix merged on Oct. 2, 2025.

    U.Today

  7. Independent corroboration

    Independently corroborated by Unchained

    Bitcoin Core Discloses Bugs That Could Freeze Mining Nodes

    Unchained

  8. Official statement

    Official statement from Bitcoin.com News

    Bitcoin Core Discloses High-Severity Security Bug That Could Halt Mining Nodes

    Bitcoin.com News

  9. Update

    Eugene Siegel identified the compact-block bug

    Crypto News reported the CVE-2025-62859 weakness was identified in April 2025.

    Crypto News (CryptoNews.net)

How coverage built up

Independent sources over time, counted the way the consensus panel counts them: a republication of a wire story does not move the line.

11 Nov, 07:578 independent sources12 Nov, 16:00
  • 11 Nov 2026, 07:57 UTC: Bitcoin Insider — 1 independent source, 1 reports
  • 11 Nov 2026, 15:22 UTC: U.Today — 2 independent sources, 2 reports
  • 11 Nov 2026, 16:30 UTC: Unchained — 3 independent sources, 3 reports
  • 11 Nov 2026, 16:58 UTC: Decrypt — 4 independent sources, 4 reports
  • 11 Nov 2026, 17:01 UTC: CryptoPotato — 5 independent sources, 5 reports
  • 11 Nov 2026, 19:46 UTC: Bankless — 6 independent sources, 6 reports
  • 11 Nov 2026, 23:05 UTC: Bitcoin.com News, official — 7 independent sources, 7 reports
  • 12 Nov 2026, 16:00 UTC: Brave New Coin — 8 independent sources, 9 reports

Affected entities

Original sources