The bugs were fixed a year ago, but you're only hearing about them now because that's how Bitcoin's security disclosure works when the stakes are this high.
The Summary
- Bitcoin Core patched three vulnerabilities in October 2025, holding disclosure until the last vulnerable release reached end of life on October 27, 2026
- The high-severity bug could freeze mining nodes, halting block production until manual restart, while a separate Tor vulnerability let thousands of nodes trust any stranger
- None of the flaws enabled coin theft, focusing instead on denial-of-service and privacy vectors
- No exploitation attempts were reported during the 13-month window between patch and disclosure
The Signal
Bitcoin Core just published details on three security vulnerabilities that have been patched for over a year. The disclosure timing matters. The team waited until version 29.x reached end of life before going public, giving stragglers time to upgrade without painting a target on their backs. It's the same responsible disclosure playbook that serious infrastructure projects follow: fix first, announce later, only when the blast radius is small enough.
The most severe bug affected block template creation. If triggered, a mining node would stop producing blocks entirely until someone manually restarted it. Not a theft vector, but a denial-of-service attack that could have knocked miners offline during critical moments. For solo miners or smaller pools, that's lost revenue. For the network, it's a potential coordination problem if enough hashpower went dark simultaneously.
"The most serious bug was capable of halting a miner's ability to build new blocks."
The Tor vulnerability is arguably more interesting from a privacy angle. Thousands of nodes running over Tor could have been manipulated into trusting arbitrary peers, compromising the anonymity that Tor users specifically opted into. This wasn't about stealing bitcoin. It was about deanonymizing node operators who took extra steps to stay private. The implications for activists, journalists, or anyone running infrastructure in hostile jurisdictions are obvious.
The third bug rounds out the denial-of-service theme. All three flaws targeted availability and privacy, not funds. That's worth noting because it reflects where Bitcoin's attack surface actually lives in 2026. Direct theft via protocol bugs is vanishingly rare. The real vectors are disruption, surveillance, and grinding the network to a halt. These aren't headline-grabbing hacks. They're the boring, grinding work of keeping a $2 trillion network operational.
Key takeaways:
- High-severity mining bug: denial-of-service via block template creation
- Tor privacy bug: node deanonymization for thousands of privacy-focused operators
- No theft vectors, no reported exploits, 13-month disclosure delay
What's striking is the discipline. Bitcoin Core held the details for over a year, long enough for even the slowest adopters to upgrade. No leaks, no exploits, no drama. That's the unglamorous side of running critical infrastructure. You find the bugs, you fix them quietly, and you only talk about it when talking can't cause harm.
The Implication
If you're running Bitcoin infrastructure, this is your regular reminder that upgrade cycles matter. The gap between patch and disclosure is a grace period, not an invitation to procrastinate. For miners, the block template bug is a case study in why redundancy and monitoring beat hoping your node stays healthy. A frozen miner is revenue walking out the door.
For privacy-focused node operators, especially those on Tor, the message is blunt: your threat model includes protocol-level bugs that compromise anonymity before they touch your coins. Stay current, or accept that you're running last year's security posture in this year's threat landscape.
Sources
CoinDesk | Bankless | Decrypt | Unchained Crypto | The Block