Bitcoin Core · security
Bitcoin Core's Three Patched Bugs: What Risk Remains for the Network?
The three vulnerabilities disclosed by Bitcoin Core on November 10, 2026, had already been fixed in 2025 releases; any remaining exposure depends on whether node operators and miners have upgraded from affected versions. The disclosures describe historical software vulnerabilities, not a newly reported network attack.【turn528866view0】【turn528866view1】【turn528866view2】
What vulnerabilities did Bitcoin Core disclose?
Bitcoin Core disclosed three vulnerabilities: a Tor permissions flaw that caused thousands of reachable mainnet nodes to trust incoming connections, a mempool bug that could prevent affected mining nodes from producing valid block templates until restarted, and a third flaw allowing malicious peers to stall block processing for 10 minutes, potentially repeatedly under specified conditions.【turn528866view0】【turn528866view1】【turn528866view2】
Orbitrum Investor Impact
Why do these vulnerabilities matter to Bitcoin investors?
The direct investment concern is network reliability: the vulnerabilities could weaken node-level denial-of-service and privacy protections, interrupt block processing, or temporarily prevent affected miners from building blocks. However, the advisories do not describe changes to BTC issuance or monetary rules, and CoinDesk reported that the high-severity mining advisory did not report attacks.【turn528866view0】【turn528866view1】【turn528866view2】【turn279441view0】
Are Bitcoin nodes still vulnerable to these bugs?
Bitcoin Core fixed the Tor permissions and mining-template vulnerabilities in versions 28.3, 29.2 and 30.0; the block-processing vulnerability was fixed in versions 29.2 and 30.0. Operators running affected earlier releases need to upgrade to versions containing the relevant fixes.【turn528866view0】【turn528866view1】【turn528866view2】
Why did Bitcoin Core disclose the vulnerabilities more than a year after fixing them?
Bitcoin Core normally delays detailed disclosure of medium- and high-severity vulnerabilities until two weeks after the last affected release series reaches end of life. The 29.x series reached that point on October 27, 2026, and the three advisories were publicly released on November 10, following the disclosure policy.【turn279441view0】【turn528866view0】【turn528866view1】【turn528866view2】
What should Bitcoin investors watch after the disclosures?
The practical issue is whether node operators, infrastructure providers and mining services have upgraded to the fixed releases. The advisories identify the affected versions and remediation but do not establish quantified financial losses or specify a further scheduled protocol change.
Sources
- CoinDesk — Bitcoin Core reveals bug that made thousands of nodes trust any stranger on Tor
- Bitcoin Core — CVE-2025-62860 - Inbound Tor connections wrongly receive -whitelist permissions
- Bitcoin Core — CVE-2025-62861 - Block template creation halted by TRUC sibling eviction during reorg
- Bitcoin Core — CVE-2025-62859 - Block processing stall via witness malleation
Original signal: CoinDesk ↗
Continue researching
Projects mentioned in this Signal
Continue your research in Orbitrum. Access to full expert research depends on each expert's offer.
Explore by sector
Explore the sectors behind this story
See more Orbitrum in Google
Add Orbitrum as a Preferred Source to make our research more likely to appear for you in Google Search.

