Bitcoin Core Discloses Three Patched Bugs, Including High-Severity Mining Node Flaw
Bitcoin Core disclosed three patched vulnerabilities on 10 November 2026, including a High-severity bug that could halt block template creation on mining nodes. Here is how to check and upgrade your node.
Crypto Support & Research Desk
Quick answer: On Tuesday, 10 November 2026, Bitcoin Core disclosed three already-patched vulnerabilities. The most serious, CVE-2025-62861 (High), could stop a mining node from building block templates after a reorg until it was restarted. Nodes on Bitcoin Core 28.3, 29.2, 30.0 or later are fixed. Older versions should be upgraded now.
What Bitcoin Core disclosed
Bitcoin Core discloses Medium and High severity issues about two weeks after the last affected release line reaches end of life. The 29.x line reached end of life on Tuesday, 27 October 2026, and the three advisories went public on 10 November. The Block covered the disclosures on 11 November, noting that affected miners had to restart nodes to produce valid templates again.
The fixes have been available for about a year. The risk today is to node operators who never upgraded.
CVE-2025-62861 (High): block template creation halted
The official advisory for CVE-2025-62861 is titled "Block template creation halted by TRUC sibling eviction during reorg."
What went wrong
During a chain reorganisation, transactions from disconnected blocks are put back into the mempool with limits bypassed. Sibling eviction, a mempool feature added in version 28.0, was not gated on that bypass flag. In the wrong circumstances it could evict a transaction while leaving its descendants in the mempool. The mempool would then contain transactions spending outputs that no longer existed, and block template creation would fail until the node was restarted.
Who was affected
- Versions 28.0 to 28.2 and 29.0 to 29.1.
- The practical impact falls on mining nodes and pools that build block templates from their own Bitcoin Core node.
Fixed versions
The fix shipped in 30.0 (10 October 2025), 29.2 (14 October 2025) and 28.3. The issue was reported by Niklas Goegge on 26 September 2025, and Greg Sanders' fix (PR #33504) was merged on 2 October 2025.
CVE-2025-62859 (Medium): block processing stall
The advisory for CVE-2025-62859 describes "Block processing stall via witness malleation."
A malicious peer could stall block processing for up to 10 minutes, the GETDATA timeout. If the attacker controlled all three of a node's high-bandwidth peers, or the node ran with -blocksonly, the stall could repeat indefinitely.
- Affected: versions before 29.2 and 30.0.
- Fixed: 30.0 and 29.2.
- Reported by Eugene Siegel on 28 April 2025; fix PR #32646 merged on 30 June 2025.
CVE-2025-62860 (Medium): Tor peers given whitelist permissions
The advisory for CVE-2025-62860 explains that inbound Tor connections could wrongly receive -whitelist permissions.
This only affected nodes using the non-default -whitelist option with an address range that included the Tor proxy IP. Bitcoin Core says some vendors bundling Tor set things up this way, which caused "thousands" of reachable mainnet nodes to whitelist all inbound Tor peers. Whitelisted peers bypass denial-of-service limits and some privacy protections.
- Affected: versions before 28.3, 29.2 and 30.0, but only with the configuration above.
- Fixed: 28.3, 29.2 and 30.0.
- Reported on 12 September 2025 by Martin Zumsande and Antoine Poinsot; fix PR #33395.
Who needs to act
- Solo miners and mining pools running Bitcoin Core 28.0–28.2 or 29.0–29.1 should treat CVE-2025-62861 as urgent.
- Node-in-a-box users (home node bundles that include Tor) should check their version and whitelist settings.
- Anyone running an older Bitcoin Core node should upgrade to a supported release.
- Exchange and mobile wallet users do not need to act. Your provider runs its own infrastructure.
How to check your Bitcoin Core node
1. Check your version. Run bitcoin-cli -version or bitcoin-cli getnetworkinfo and look at the subversion field. If you use a node bundle, check the app's settings page.
2. Compare with the fixed versions. You are covered for all three issues on 29.2 or 30.0 and later. On the 28.x line, 28.3 covers CVE-2025-62861 and CVE-2025-62860, but not CVE-2025-62859.
3. Review whitelist settings. Look in bitcoin.conf for whitelist= lines. If a range covers your Tor proxy address (often 127.0.0.1), the CVE-2025-62860 configuration may apply on unpatched versions.
4. Back up first. Before upgrading, back up any wallet files and your configuration.
5. Download only from official sources. Get releases from bitcoincore.org and verify the signatures and checksums, or update through your node bundle's official app store.
6. Restart and confirm. After upgrading, confirm the new version and that the node syncs normally.
Mining operators: extra checks
If you build templates with Bitcoin Core:
- Monitor
getblocktemplatefor errors, especially after reorgs. - Alert on long gaps without a new template.
- Keep a documented restart procedure while you schedule the upgrade.
Upgrading removes the root cause; restarts only clear the symptom.
Why disclosure happens after the fix
Bitcoin Core's policy is to give operators time to upgrade before details are public. That is why advisories describe issues fixed a year earlier. It also means older nodes become easier targets once details are out, so the disclosure date is a good trigger for upgrading.
Node security also includes infrastructure credentials and the software you install alongside your node. See our guides to rotating node credentials after the Chainstack incident and fake AI trading tools that spread wallet malware. Other network upgrades this month are covered in our articles on Dash v24 and Hedera v0.79.
What is not known
No public source gives a count of nodes still running affected versions. Secondary reports say no active attacks or public exploit tools were confirmed, but Bitcoin Core's advisories do not make that claim, so treat it as unverified.
Frequently asked questions
Which Bitcoin Core versions fix CVE-2025-62861?
Bitcoin Core 30.0, 29.2 and 28.3 include the fix. Versions 28.0 to 28.2 and 29.0 to 29.1 were affected.
Do I need to do anything if I keep bitcoin on an exchange or mobile wallet?
No. These bugs affect people who run their own Bitcoin Core node. Your exchange or wallet provider manages its own infrastructure.
What did the High severity bug do?
After a chain reorganisation, a mempool eviction flaw could leave transactions spending non-existent outputs, which stopped the node from creating block templates until it was restarted. That mainly affects miners.
Is my Tor node affected by CVE-2025-62860?
Only if it runs a version before 28.3, 29.2 or 30.0 and uses the non-default whitelist option with a range that includes the Tor proxy address.
Why were these bugs disclosed a year after the fix?
Bitcoin Core discloses Medium and High issues about two weeks after the last affected release line reaches end of life, giving operators time to upgrade first.
Conclusion
The three Bitcoin Core advisories describe bugs that were fixed in late 2025 but are now public. If you run a node, check your version today, review any whitelist settings, and upgrade to 29.2, 30.0 or later from official sources. Miners on 28.x or early 29.x builds should prioritise the High severity template bug.
This article is for general information only and is not financial or professional security advice. Blockchain Support USA is an independent publication and is not affiliated with Bitcoin Core, any exchange or any wallet provider. We will never ask for your seed phrase, private keys, passwords or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.