
Key takeaways
- Bitcoin Core discloses three vulnerabilities that its October 2025 releases already fixed, and the advisory reports no attacks
- Thousands of Bitcoin Core nodes using the non-default whitelist setting trusted all incoming Tor connections as local
- Bitcoin Core's high-severity mining bug could stop affected nodes creating valid block templates after a chain reorg
Three Flaws, Fixed a Year Ago
Bitcoin Core published advisories for three vulnerabilities, all of them already fixed in releases from October 2025. Bitcoin Core 30.0 shipped with fixes for all three on Oct. 10, 2025, followed by version 29.2 on Oct. 14, 2025.
No funds were at risk, and none of the three bugs can be used to steal coins or create new bitcoin. The advisory does not report any attacks.
Bitcoin Core held the disclosures until the last affected series, 29.x, reached end of life on Oct. 27, 2026. The project normally publishes advisories two weeks after the last affected release is out of support.
Strangers on Tor Got Trusted Status
The medium-severity flaw, listed in the Common Vulnerabilities and Exposures (CVE) catalog as CVE-2025-62860, left thousands of reachable mainnet nodes using the non-default whitelist setting whitelisting all incoming Tor connections. Strangers connecting through Tor could bypass spam and privacy protections because the software treated them as trusted computers.
Providers bundled Bitcoin Core with Tor, so incoming Tor connections appeared to come from the local Tor software. If that address fell inside the whitelisted range, outside visitors inherited trusted permissions. Nodes that never enabled the whitelist setting were unaffected. The fix, pull request 33395, stops applying address-based whitelist permissions to Tor inbound peers.
Mining Nodes Could Stall in Silence
The high-severity flaw, CVE-2025-62861, could leave an affected mining node unable to create valid block templates after a chain reorganization, or reorg, until it was restarted.
A rule introduced in Bitcoin Core 28.0 for evicting sibling transactions could remove a transaction restored to the mempool after a reorg while leaving its descendants, so the node tried to build blocks with transactions whose inputs were missing. Affected miners had to restart their nodes before they could create valid block templates again.
For node runners, the checklist is short: confirm your node is current, review Tor and whitelist settings, and if you mine, alert on zero blocks produced rather than mere uptime.
Why It Matters
A Bitcoin node exists so you can verify the chain without trusting anyone, yet this Tor flaw handed trusted status to strangers on thousands of nodes that used the whitelist setting. The mining bug carries the same lesson for hash power, because a mining node could stay online and still stop creating valid block templates after a reorg, so uptime alone proves nothing. Bitcoin Core published advisories for all three vulnerabilities after the fixes shipped in releases from October 2025, an open-source verification culture no custodian or closed platform offers its users. Sovereignty is a habit, not a purchase: run current Bitcoin Core releases, review your Tor and whitelist settings, and alert on zero blocks produced rather than mere uptime.




















