Bitcoin Core, the software most bitcoin nodes run, published three security advisories on Tuesday for bugs it fixed more than a year ago. One is rated High: under the right conditions it could leave a mining node unable to build a valid block until someone restarted it.

All three were fixed in Bitcoin Core 30.0 on 10 Oct 2025 and in the 29.2 point release on 14 Oct; 28.3, later that month, carried two of the fixes. The last affected version line, 29.x, reached end of life on 27 Oct this year, and the details went public on 10 Nov, the advisories show. If your node runs 30.0 or later, or 29.2 or later on the 29 line, you already have all three.

The three bugs

The serious one is for miners. A reorg, short for chain reorganisation, is when a node swaps the latest blocks for a competing set. The transactions from the dropped blocks go back into the mempool, the node’s waiting room for unconfirmed transactions. Bitcoin Core does that deliberately without applying its usual relay rules.

One rule slipped through.

Version 3 or “TRUC” transactions may have only one unconfirmed child in the mempool, and since 28.0 a newer child can push out the old one, which Bitcoin Core calls sibling eviction.

During a reorg that eviction still ran, so it could remove a transaction while leaving its descendants behind, the CVE-2025-62861 advisory says. The mempool then held transactions spending coins that no longer existed, and every block template the node assembled failed its own validity check. A restart fixed it.

Versions 28.0 to 28.2 and 29.0 to 29.1 were affected. Niklas Goegge reported it on 26 Sep 2025, and Greg Sanders opened the fix three days later.

The second lets a hostile peer slow you down. A compact block is the slimmed-down way nodes pass new blocks around. A peer, meaning another node yours is connected to, could send one with tampered witness data, the signature part of a transaction. Older versions then fell back to asking that same peer for the full block, with a 10-minute timeout, according to CVE-2025-62859. An attacker who controlled all three of a node’s high-bandwidth peers, or who targeted a node running -blocksonly, could repeat that indefinitely. Eugene Siegel reported it in April 2025. It is rated Medium.

The third was common in packaged nodes. The -whitelist setting tells a node to trust certain peers and drop some denial-of-service limits and privacy protections for them. Inbound Tor connections arrive from the address of the local Tor daemon, so a whitelist covering that address range also trusted every Tor peer, CVE-2025-62860 explains. Popular node bundles set it up exactly that way, and the advisory says “thousands of reachable mainnet nodes” ended up trusting every Tor peer that connected to them. Martin Zumsande and Antoine Poinsot reported it in September 2025 and also told the maintainer of Bitcoin Knots. Nodes that never set -whitelist were not affected. Medium.

None of the advisories says any of the bugs was used against anyone.

What this does to my base case

Two weeks ago I wrote about three LLM-found bugs fixed in October, the first test of the fast-fix policy. My base case, the short fuse, was that more bugs would be fixed and disclosed within days.

Tuesday’s batch is the other track, and it still exists.

These bugs were fixed quietly, then held back until the last vulnerable version line was out of support. That is roughly 13 months from fix to disclosure for the High-severity one. I read it as a two-speed project rather than a change of mind: bugs anyone could find go out fast, the rest wait for the old versions to die off.

What would change my view is a High-severity bug that was easy to find but still sat under embargo. Nothing here suggests that.

What to check

If you mine on your own node, confirm the version is 30.0 or later. If you run a packaged node with Tor, check that the software has been updated since October 2025 and that -whitelist does not cover your Tor daemon’s address.

Related: Bitcoin Core later fixed an LLM-found bug that let a hostile peer stall nodes, in versions 30.5 and 31.3

This article is for information only and is not investment advice.