
Instantly create stunning AI-powered web apps and games for your next big project on Asvoria.app. No coding. No waiting. Just launch.
Bitcoin Core Discloses Three Previously Fixed Node Vulnerabilities
November 12, 2026 at 7:00 AMby The Block Whisperer
+1
+0
New disclosures explain older mining, Tor-permission and block-processing bugs already addressed in software releases.
Bitcoin Core developers published three security disclosures on November 10, explaining vulnerabilities that had already been fixed in earlier releases. One issue was rated high severity and two medium severity. The disclosures concern node behavior and operational reliability; they do not announce a new theft of bitcoin or a change to Bitcoin’s supply rules.
The highest-rated issue, CVE-2025-62861, involved transactions being restored after a chain reorganization. A mismatch in mempool handling could leave a miner unable to create valid block templates until the node restarted. Versions 28.0–28.2 and 29.0–29.1 were affected, with fixes included in 28.3, 29.2 and 30.0.
CVE-2025-62860 involved inbound Tor connections incorrectly receiving privileges intended for trusted peers when an operator configured a matching IP whitelist. Nodes without that non-default whitelist setting were not affected. The corrected behavior prevents those inbound Tor peers from inheriting the extra permissions.
CVE-2025-62859 concerned the order of checks during compact-block handling. Under particular conditions, a malicious peer could stall a node’s block processing, potentially repeating the delay. That issue was fixed in 29.2 and 30.0. Together, the reports illustrate why software version and local configuration both matter when evaluating exposure.
The publication dates should not be confused with the dates when developers first learned about the problems. Each advisory includes a timeline covering private reporting, code changes and release milestones. This allows operators to compare their deployment history with the vulnerable periods instead of assuming every currently running node has the same risk.
For mining businesses, interrupted template production has a different practical consequence from a consumer wallet interface becoming unavailable. Likewise, an overly broad permission setting affects the trust boundary around network peers. Treating all three reports as a single generic Bitcoin exploit would hide those operational differences.
The useful follow-up is an inventory of actual node versions, packaged dependencies and configuration choices. A server can appear healthy while running an obsolete component inside a larger product. These disclosures give operators concrete identifiers to check with software providers and demonstrate why a completed upgrade needs to be verified across the whole deployment.
Explore more articles like this
Subscribe to Asvoria News to receive all the latest news.
Stay ahead with exclusive press releases and expert insights on Web3 and the Spatial Web. Be the first to hear about Asvoria’s latest innovations, events, and updates. Join us — subscribe today!
Editor’s choice
© 2026 Asvoria. All rights reserved.
Avoria does not endorse or promote investment in any of the tokens or NFT projects featured on this platform.
We accept no responsibility for any losses incurred. Users should conduct their own research and consult with a financial advisor before investing.
For more information about Doing Your Own Research (DYOR), please visit this link.