Bitcoin Core discloses three already-patched flaws, including a mining-node stall

Bitcoin Core published three security advisories on 10 November, including a high-severity flaw that could stop affected mining nodes creating block templates after a chain reorganisation. The fixes shipped in 2025; the disclosure does not announce a new Bitcoin network outage.

The mining flaw, CVE-2025-62861, affected versions 28.0–28.2 and 29.0–29.1. During a reorganisation, transactions from disconnected blocks return to the node's waiting pool. An error in handling a particular transaction type could leave that pool inconsistent, causing newly assembled block templates to fail validation. A restart could restore consistency, but installing a fixed release addresses the underlying defect. The advisory lists fixes in 30.0, 29.2 and 28.3.

The other advisories cover different conditions. CVE-2025-62860 concerns incoming Tor connections receiving permissions intended for trusted peers when an operator had configured the non-default whitelist option. That could lift denial-of-service limits and privacy protections. Nodes without that option were never affected; the listed fixes are 28.3, 29.2 and 30.0. CVE-2025-62859 describes a malicious peer stalling block processing through compact-block handling, fixed in 29.2 and 30.0.

These are operator-facing software issues, rather than evidence that ordinary wallet balances have disappeared. The useful response is to check the installed Bitcoin Core version and configuration against each advisory and move to a currently supported release. Public disclosure follows the project's security timetable: the mining advisory records the last vulnerable release line reaching end of life on 27 October 2026. A patch's original release date and the date its details become public are therefore different milestones.