Bitcoin Core published details of three vulnerabilities on November 10, 2026: CVE-2025-62861 (High severity), CVE-2025-62860 and CVE-2025-62859 (both Medium). All three were fixed more than a year ago, in Bitcoin Core 30.0 of October 10, 2025 and in the 29.2 and 28.3 maintenance releases that followed. A node on 30.0 or later is not affected by any of them.
None of the three lets anyone take coins. They can stall a node’s block processing, stop a mining node from building blocks, or lift anti-abuse limits for strangers who connect over Tor.
Is my node affected?
Run bitcoin-cli -version or check subversion in bitcoin-cli getnetworkinfo, then find your version below. The table combines the affected ranges stated in the three advisories.
| Version you run | CVE-2025-62861 (High) | CVE-2025-62860 (Medium) | CVE-2025-62859 (Medium) |
|---|---|---|---|
| 27.x or older | Not affected | Affected if -whitelist is set | Affected |
| 28.0 to 28.2 | Affected | Affected if -whitelist is set | Affected |
| 28.3, 28.4 | Fixed | Fixed | Affected (no 28.x fix listed) |
| 29.0, 29.1 | Affected | Affected if -whitelist is set | Affected |
| 29.2 to 29.5 | Fixed | Fixed | Fixed |
| 30.0 and later | Fixed | Fixed | Fixed |
Being fixed for these three is not the same as being supported. The project maintains the latest three major versions, and since Bitcoin Core 32.1 came out on October 27, 2026, that means 30.x, 31.x and 32.x; 29.x reached end of life that day. The point releases of October 27 and 28 (32.1, 31.2, 30.4 and a final 29.5) also fixed three easily discoverable bugs disclosed on October 28, including a memory exhaustion through TCP urgent data on non-Linux systems. As of November 16 the versions that are both fixed and maintained are 30.4, 31.2 and 32.1.
What each bug does
CVE-2025-62861, High. Version 3 (“TRUC”) transactions under BIP 431 may have at most one unconfirmed parent and one unconfirmed child in the mempool, but a block may contain any shape. Since 28.0, Bitcoin Core evicts an existing child when a better-paying sibling arrives, a form of replace-by-fee. During a chain reorganization that eviction logic still ran while confirmed transactions were put back into the mempool, which could leave transactions spending outputs that no longer existed. The advisory says a node in that state cannot build a valid block template until it is restarted, so the practical victims are mining nodes and pool backends.
CVE-2025-62860, Medium. Inbound Tor connections arrive from the address of the local Tor daemon. If an operator set -whitelist to an IP range that included that daemon, every inbound Tor peer received the trusted-peer permissions, which lift denial-of-service limits and privacy protections. The advisory says node bundles that ship Tor alongside Bitcoin Core set exactly such a range, which “led to thousands of reachable mainnet nodes whitelisting all incoming Tor connections.” Nodes that never set -whitelist were not affected. On an older node, bitcoin-cli getpeerinfo shows the permissions granted to each peer next to its network (onion for Tor); Bitcoin Core’s RPC reference documents both fields.
CVE-2025-62859, Medium. A peer that announced a compact block first could exploit a check order in block reconstruction and make the node wait up to 10 minutes for the full block from that same peer. If the attacker controlled all three of the victim’s high-bandwidth peers, or the node ran with -blocksonly, the stall could be repeated indefinitely.
Why the details came out a year after the fix
Bitcoin Core’s security policy discloses Medium and High bugs two weeks after the last affected release line reaches end of life. Here that was 29.x on October 27, 2026, so publication fell on November 10. The 32.1 release notes had pre-announced three Medium and High vulnerabilities fixed in 30.0. Bugs the project classes as easily discoverable skip the embargo, which is why the October 28 issues were published together with their fixes.
One date in the advisories disagrees: the CVE-2025-62860 timeline gives October 20, 2025 for the 28.3 release, while the CVE-2025-62861 timeline and the 28.3 release announcement say October 17.





