Key points
- Bitcoin Core published three security advisories on November 10, 2026, for bugs fixed in October 2025.
- The high-severity CVE-2025-62861 could stop a node from creating block templates after a chain reorganization.
- It affected versions 28.0 to 28.2 and 29.0 to 29.1; versions 28.3, 29.2 and 30.0 fix it.
- The two other flaws, rated medium, could stall block processing or weaken protections on some Tor-connected nodes.
- The developers report no evidence that any of the bugs were exploited, and none could steal or forge coins.
The developers of Bitcoin Core, the most widely used software for running a Bitcoin node, have disclosed three vulnerabilities, including one that could have stopped a miner's node from producing blocks. All three were fixed in releases shipped in October 2025, and the developers say they have no evidence any of them were exploited, Decrypt reported.
The advisories, published on bitcoincore.org on November 10, 2026, describe denial-of-service and privacy problems. None of them allowed anyone to steal or forge coins, and none reached Bitcoin Core's "critical" severity tier.
The mining bug
The most serious flaw, CVE-2025-62861, is rated high severity. It concerns what happens during a chain reorganization, or reorg, when a node briefly follows one version of the latest blocks and then switches to a competing version, putting transactions from the abandoned blocks back into its mempool, the waiting room for unconfirmed transactions explained in our guide to fees and the mempool.
The bug involved TRUC transactions, a newer transaction type with strict limits on how many unconfirmed parent and child transactions it can have. A feature added in Bitcoin Core 28.0, called sibling eviction, could wrongly remove a restored transaction during a reorg while leaving its children behind. The mempool then held transactions spending coins that no longer existed in it.
