Bitcoin Core: 3 vulnerabilities, which version, CVEs
Bitcoin Core disclosed three vulnerabilities on 10 November, fixed in October 2025. Running 28.x or 29.x? Here is what applies to you.

The Bitcoin Core project published three security advisories on 10 November 2026 about vulnerabilities that were already fixed in October 2025. One is rated high (CVE-2025-62861): a node that went through a chain reorganisation could no longer build a valid block template until it was restarted. If you run Bitcoin Core 30.0 or newer, all three are fixed. If you run 28.0 up to and including 28.2, or 29.0 up to and including 29.1, you are behind.
Bitcoin Core vulnerabilities in short
- What happened: on 10 November 2026, Bitcoin Core published the advisories CVE-2025-62861 (high), CVE-2025-62859 (medium) and CVE-2025-62860 (medium).
- How long ago the fix came: version 30.0 was released on 10 October 2025, version 29.2 on 14 October 2025 and version 28.3 later in October 2025. That puts 13 months between the first release with the fix (30.0) and the disclosure.
- Who is affected: only people who run a Bitcoin Core node themselves. If you use an exchange or a wallet app, you are not running this software.
- The most serious point: with CVE-2025-62861, a mining node could no longer build blocks after a chain reorganisation until it was restarted. Affected versions: 28.0 up to and including 28.2, and 29.0 up to and including 29.1.
- What you should do: check your version and update to 30.0 or newer. The 29.x series reached end of life on 27 October 2026.
- What the advisories do not contain: a report that the flaws were exploited. That does not mean it never happened (see below).
What the three advisories say
All the details below come from the three advisories on bitcoincore.org, read on 16 November 2026.
CVE-2025-62861: the mempool gets out of balance (high)
Bitcoin Core applies extra restrictions to version 3 transactions (TRUC, described in BIP 431): such a transaction may have at most one unconfirmed parent and one unconfirmed child. These are transaction relay rules, not consensus rules. A valid block may therefore contain a TRUC transaction with several children.
The problem arose during a chain reorganisation. Transactions from the disconnected blocks then go back into the mempool, and that is supposed to happen without the usual limits. Because of the bug, so-called ‘sibling eviction’ (replacing an existing child) still took place. As a result, a transaction that had been put back could be removed while the transactions building on it stayed in place. The mempool then held transactions that spent outputs which no longer existed.
The consequence according to the advisory: the block template the node assembles fails its own validity check, and the node can no longer create blocks until it is restarted.
The bug was reported by Niklas Goegge on 26 September 2025. By 2 October 2025 the fix had been merged into the main codebase (PR #33504).
CVE-2025-62859: a block that hangs for ten minutes (medium)
With a compact block (an economical way to relay a block), Bitcoin Core cleared the download state before it had checked for tampering with the witness data. If that check failed, the node requested the block again from the same peer, with a waiting time of 10 minutes. A malicious peer that was the first to announce a compact block could therefore hold up processing. If the attacker controlled all three of the victim's high-bandwidth peers, or if the victim ran with -blocksonly, this could repeat indefinitely. The reporter was Eugene Siegel (28 April 2025).
CVE-2025-62860: Tor connections with too many permissions (medium)
An incoming Tor connection reaches Bitcoin Core with the IP address of the Tor service, which usually runs on the same machine or the same network. The non-default -whitelist setting removes a range of limits against overload and privacy leaks for trusted peers. If the address of the Tor service fell within the configured IP range, incoming Tor peers received those permissions too. Only nodes that had set -whitelist were affected.
The advisory says that popular vendors shipped Bitcoin Core together with a Tor service and set -whitelist to the range of that service. It mentions thousands of reachable nodes on the main network that, as a result, trusted all incoming Tor connections. The reporters were Martin Zumsande and Antoine Poinsot (12 September 2025).
Why only now, 13 months after the first fix release?
The fixes were already in the October 2025 releases, but the details were only made public on 10 November 2026. In the advisories' timeline, the last step before disclosure is the end of life of the 29.x series, the last vulnerable series, on 27 October 2026. Publication followed on 10 November. We have not read the project's policy document on this point; the order above is what the timelines show.
For the reader, this is the practical point: if you moved to 30.0 or newer in October 2025 or later, you do not need to do anything. If you stayed on 28.x or 29.x because ‘it works’, the details of three known holes are now out there, and attackers can read them too.
What does this mean for you as a European investor?
You use an exchange or a wallet app. Then you do not run a Bitcoin Core node yourself, and these advisories do not affect you directly. No action is needed. For safe storage in general, see our crypto security checklist.
You run your own node. Check your version with bitcoind --version or bitcoin-cli --version (or through the menu of your node package, if you use a ready-made package) and move to 30.0 or newer. If you run a package that ships Bitcoin Core with Tor and uses -whitelist, check whether the vendor has released a new version. We do not know which packages this concerns.
You mine at home. If your Bitaxe or other home miner uses a pool, the pool builds the block template, not your machine; whether any pool was affected, we do not know. The advisory mainly concerns people who use their own node as the source of block templates, for example in solo mining. More on that route: solo mining with your own pool or node. On home mining, we previously wrote about the difficulty drop of 14 November.
Your country makes no difference here. This is software, not a rule. There are no separate requirements for the Netherlands, Belgium, Germany, France, Spain, Portugal or Poland.
Want to know where an earlier privacy problem in Bitcoin Core was found? That is in our piece on the IP leak in Bitcoin Core 31.0.
What is not certain yet
- Exploitation: in the three advisories we found no report of exploitation in the wild. That does not mean it never happened; an attack on a single node does not always get noticed. The Block, which wrote about the advisories on 11 November, says that Bitcoin Core reports no active exploitation: that is a second source, not a finding of our own.
- Whether 28.x was affected by CVE-2025-62859: the advisory lists only 29.2 and 30.0 as fixed and does not say what applied to 28.x. The 28.3 fix is mentioned in the other two advisories.
- The date of version 28.3: the advisories give two dates: 17 October 2025 in the advisory on CVE-2025-62861 and 20 October 2025 in the advisory on CVE-2025-62860. We therefore say only ‘October 2025’.
- Which packages were affected: the advisory on CVE-2025-62860 mentions ‘popular vendors’ without naming them. Which ones they are is not stated.
- Whether mining pools were affected: the advisory on CVE-2025-62861 describes the consequence for a node that creates blocks, not which pools ran such a node.
- The current latest version: we do not name a latest version; check the project's download page for that.
This article is not investment advice. Crypto can fall sharply in value and you can lose your entire stake.
Frequently asked questions
Do I need to move my bitcoin because of these vulnerabilities?
No, none of the advisories is about theft of coins or keys. The flaws concern how a node relays and processes blocks and transactions, and the permissions of Tor peers. Even if you run a vulnerable node, you do not need to move your coins.
Which version of Bitcoin Core do I need?
Version 30.0 or newer contains the fixes for all three. Version 29.2 does too. According to the advisories, version 28.3 contains the fixes for CVE-2025-62861 and CVE-2025-62860; whether 28.x was affected by CVE-2025-62859, the advisories do not say. The 29.x series reached end of life on 27 October 2026, so 30.0 or newer is the choice that still gets maintenance.
How do I check which version I am running?
Run bitcoind --version or bitcoin-cli --version in a terminal. If you use a package with its own screen, look at its info page.
Does this affect my Bitaxe or other home miner?
A home miner itself does not run Bitcoin Core. The advisory on the mining bug concerns nodes that build block templates. If you mine through a pool, the pool builds the template.
Sources
Read on 16 November 2026.
- Bitcoin Core: CVE-2025-62861, block template halted by TRUC sibling eviction during a reorg (10 November 2026)
- Bitcoin Core: CVE-2025-62859, block processing delayed via witness malleation (10 November 2026)
- Bitcoin Core: CVE-2025-62860, incoming Tor connections receive -whitelist permissions (10 November 2026)
- Bitcoin Core: security advisories and policy
- The Block: Bitcoin Core discloses three patched security flaws (11 November 2026)
Prices of the coins in this article
Mid-market price from CoinGecko in euros, updated at 01:30 UTC.All 20 prices