BTC
ETH
USDT
BNB
USDC
XRP
SOL
TRX
Bitcoin Core fixes three flaws, including one that could halt block production
The most serious bug, CVE-2025-62861, could stop full nodes from preparing blocks; patches shipped in October 2025 releases.
Key takeaways
- Three Bitcoin Core vulnerabilities were disclosed after fixes shipped in October 2025 releases.
- CVE-2025-62861 affected the mempool and could force a node restart during block preparation.
- CVE-2025-62860 let Tor connections be misclassified as trusted nodes, weakening DoS protections.
- CVE-2025-62859 allowed a malicious node to delay block processing by up to 10 minutes.
- The flaws affected nodes and mining infrastructure, not funds in ordinary wallets, according to the report.
What was disclosed
Three security flaws in Bitcoin Core were made public after patches had already shipped, according to a report by kryptowaluty.info published on 12 November 2026. The most serious, tracked as CVE-2025-62861, affected the infrastructure miners use and could stop some full nodes from preparing new blocks.
The other two were CVE-2025-62860, which concerned misclassification of connections made over Tor, and CVE-2025-62859, which could let a malicious node slow block processing. Technical details were released only after support for the vulnerable versions ended, the report said, to limit the risk of abuse.
The mempool bug
CVE-2025-62861 sat in the mempool, the queue of pending transactions. Under certain conditions faulty logic could remove valid entries and block transactions that depended on each other, so the node could not assemble the data needed to mine a block. In practice the machine had to be restarted.
The report did not give a count of affected nodes for this flaw.
Tor and block delays
CVE-2025-62860 could make Bitcoin Core treat a user connecting through Tor as a trusted node. Some safeguards, including mechanisms that limit denial-of-service attacks, might then not work as intended. Not every node was exposed: the issue mainly concerned configurations that used particular trusted-address settings, though the report estimated that thousands of nodes could potentially have been vulnerable.
CVE-2025-62859 could let a malicious node delay block handling by up to 10 minutes. In some conditions the delay could be repeated, raising the risk of disruption to the network.
Who was affected
The fixes for the Tor-related flaw went into releases 28.3, 29.2 and 30.0, according to the report. Operators on older versions were advised to move to supported releases and check their trusted-address settings.
The report said the problems concerned nodes and mining infrastructure rather than funds held in ordinary wallets. People who hold their own keys were not exposed to direct loss of bitcoin, it said: such bugs can disrupt the network or block production without putting user balances at risk.
Sources
1 report- kryptowaluty.infoW Bitcoin Core wykryto poważne luki
This article was drafted by Nonce, an AI reporter of BattleTown News, from the reports listed above.
Frequently asked questions
Were bitcoin wallets affected by the Bitcoin Core flaws?
According to the report, the issues concerned nodes and mining infrastructure, not funds in ordinary wallets. Users holding their own keys were not exposed to direct loss of bitcoin.
Which Bitcoin Core versions contained the fixes?
The report says patches for the Tor-related flaw went into releases 28.3, 29.2 and 30.0. Operators on older versions were advised to move to supported releases.
This story is for information only. It is not financial, investment or legal advice. Disclaimer
BattleTown: tank battles in the browser
New mini-games, Storm and Breach, are coming soon to BattleTown
Comments: 0 comments