
Bitcoin Core Security Flaws Include Bug That Could Halt Mining Nodes
Bitcoin Core, the reference software that powers most nodes on the Bitcoin network, has disclosed three security flaws that were quietly fixed in releases last year. One of them, a high-severity bug, could have stopped a mining node from producing blocks altogether. The disclosure, published on November 10, 2026, is a reminder that even the most battle-tested software in cryptocurrency carries hidden weaknesses. None of the three flaws was exploited, and none put user funds at risk, created new coins, or threatened the consensus rules that hold the network together. Yet the most serious flaw, tracked as CVE-2025-62861, struck at something fundamental: the ability of a mining node to do its job. For a network whose security depends on miners competing to add new blocks, a bug that can silence a miner is not minor, even if it was caught before it did damage.
What Bitcoin Core disclosed on November 10
The disclosure covered three vulnerabilities, all patched in Bitcoin Core releases published in October 2025. One was rated high severity and two were rated medium severity. The flaws were announced together, more than a year after the first was reported and more than a year after the fixes shipped. That long gap was not an accident. It followed the project’s disclosure policy, which delays public announcements until every affected release line has reached the end of its life, so users who have not upgraded are not handed a roadmap for attacking them. The policy is a trade-off the project has defended for years: staying quiet protects slow upgraders, but it also means the public learns about serious bugs long after they were fixed. A snapshot of reachable nodes taken on November 11 showed that around 1,885 of 20,342 reachable nodes, roughly 9 percent, were still running versions affected by at least one of the three flaws.
The CVE-2025-62861 mining bug
The most serious of the three Bitcoin Core security flaws is CVE-2025-62861, a high-severity vulnerability involving TRUC transactions, also known as version 3 transactions, a relatively new transaction type introduced under BIP 431. TRUC, short for Topologically Restricted Until Confirmation, is a design meant to make certain transactions more predictable and safer to handle, particularly those used by second-layer protocols. The vulnerability arose in the interaction between those new rules and one of the oldest events in a blockchain: a chain reorganisation. A reorganisation happens when two competing versions of the blockchain exist briefly and the network settles on one of them, discarding blocks from the other. Node software must handle it cleanly; in this case, it did not. After a reorganisation, a mining node’s memory pool, the waiting area for unconfirmed transactions, could become corrupted so that every block template the node tried to build failed its own validity check. If the template cannot pass validation, the miner cannot produce a block at all. The consequence is plain: the node cannot produce blocks until it is restarted. The flaw was reported by Niklas Goegge on September 26, 2025, and fixed by Greg Sanders in pull request 33504, merged on October 2, 2025, by gating the TRUC checks on bypass limits. The Bitcoin Core 30.0 patch shipped on October 10, 2025, along with maintenance releases 29.2 and 28.3. The affected versions were Bitcoin Core 28.0 through 28.2 and 29.0 through 29.1.
The two medium-severity flaws
The other two vulnerabilities were rated medium severity, but each illustrates a different way that networked software can be pushed off balance. The first, CVE-2025-62859, was a denial-of-service weakness in block processing. A malicious peer could send a specially crafted compact block, with altered witness data, and thereby stall the victim node’s block processing for around ten minutes. A frozen node would fall behind the chain and stop relaying information to its peers. The flaw was reported by Eugene Siegel in April 2025, months before the mining bug was found, leaving it unannounced for well over a year. The second flaw, CVE-2025-62860, was subtler. It involved how Bitcoin Core handles connections from the Tor anonymity network when a node operator has configured a whitelist of trusted address ranges. If the proxy address used for Tor connections fell inside a whitelisted range, inbound peers arriving over Tor could silently receive the permissions normally reserved for trusted peers. Granting them by accident undermines the separation between trusted peers and strangers. Both flaws were fixed in the same October 2025 releases as the mining bug, and neither was reported as exploited.
Why the disclosure waited more than a year
The most striking feature of the November 10 disclosure is its timing. The fixes shipped in October 2025, yet the public announcement did not arrive until November 10, 2026, more than thirteen months later. The reason lies in the Bitcoin Core project’s disclosure policy, which holds back public details until the last affected release line has reached the end of its supported life. Here, that meant waiting until the 29.x line reached end of life on October 27, 2026. The announcement followed about two weeks later, on November 10. Announcing a serious flaw while many users still ran affected versions would hand attackers a detailed description of the weakness and a large population of unpatched targets. By waiting until the affected lines are no longer supported, the project ensures that anyone still running them has already been told, for months, to upgrade. Critics say the delay leaves users in the dark; supporters reply early disclosure would arm attackers first.
How many nodes are still exposed
The disclosure matters most for the nodes that have not yet upgraded, and the numbers show this is not a trivial group. A snapshot taken on November 11, using data from the Bitnodes service, found that around 1,885 of 20,342 reachable nodes, about 9 percent, were still running versions affected by at least one of the three flaws. Reachable nodes accept incoming connections and form the backbone of the network’s peer-to-peer fabric. Nine percent is a significant minority: roughly one node in eleven still carries at least one of these weaknesses, more than a year after the fixes were released. Some operators may simply not have checked for updates, or may run packaged installations that lag behind releases. The current maintained releases are Bitcoin Core 32.1, 31.2 and 30.4, and the disclosure is, in effect, a final nudge to anyone still on the 28.x or 29.x lines to move to a supported version.
What node operators and miners should do now
For anyone running a Bitcoin node, the advice following the disclosure is simple and does not depend on understanding the technical details of any of the three flaws. Upgrade to a currently maintained release, meaning Bitcoin Core 32.1, 31.2 or 30.4, and do it promptly. Mining operators should treat the advice with particular urgency, because the CVE-2025-62861 mining bug is the flaw that can directly interrupt their operations. A mining node that hits the corrupted memory pool condition after a reorganisation will not recover on its own; it needs a restart, and every minute it spends unable to produce blocks is a minute of lost revenue. Operators who cannot upgrade immediately should watch for a mining node that suddenly stops producing valid block templates, and be ready to restart it. Tor users should also check whether their proxy address falls inside any whitelisted range. Running a node means following release announcements and treating end-of-life dates as deadlines.
Why this disclosure matters for Bitcoin
It is tempting to read a disclosure like this one as bad news, but for Bitcoin the honest reading is more balanced. The flaws were real, and the most serious could have halted mining nodes, but they were found by researchers, fixed quickly, and never exploited. Bitcoin’s security rests not on perfect code but on open code: many eyes read it, researchers are rewarded for reporting problems, and fixes ship to thousands of independent operators. The disclosure also shows the limits of that model. A fix that exists but is not installed protects nobody, and nine percent of reachable nodes still running affected versions more than a year after the patch is a reminder that decentralisation has a cost. No central administrator can push an update to every node overnight; each operator must choose to upgrade.
Frequently asked questions
What are the Bitcoin Core security flaws disclosed in November 2026?
Three vulnerabilities disclosed on November 10, 2026, all patched in October 2025 releases: high-severity CVE-2025-62861, a mining bug involving TRUC transactions, plus medium-severity CVE-2025-62859, a block-processing stall, and CVE-2025-62860, a Tor whitelist issue.
What does the CVE-2025-62861 mining bug do?
It can corrupt a mining node’s memory pool after a chain reorganisation, so every block template fails its own validity check and the node cannot produce blocks until restarted. It affected Bitcoin Core 28.0 to 28.2 and 29.0 to 29.1, and was fixed in 30.0, 29.2 and 28.3.
Were any of the flaws exploited?
No. No exploits were reported, and the disclosure reported no theft, no new coins created and no consensus failure. Researchers found the flaws and they were fixed before any exploitation.
Which Bitcoin Core versions are safe now?
The current maintained releases are Bitcoin Core 32.1, 31.2 and 30.4. Around 9 percent of reachable nodes were still running affected versions in a November 11 snapshot, so operators on older releases should upgrade promptly.
Why did Bitcoin Core wait more than a year to disclose the flaws?
Its disclosure policy delays announcements until the last affected release line reaches end of life. The 29.x line reached end of life on October 27, 2026, and the disclosure followed about two weeks later.
Source: Bitcoin Insider
Related reading on MM Crypto Analysis Web
- Bitcoin Price Analysis: $71,400 Support Holds the Key to a $78,000 Bounce
- MSCI Removes Strategy From Global Indexes in November Reshuffle
- Bitcoin Price Today: Can BTC Hold $74,600 Before November 11?
More in Bitcoin on MM Crypto Analysis Web.
Pingback: Bitcoin Below $73,000: First Drop Since August Hits