CVE-2025-62861 — Bitcoin Core Mining Node Denial-of-Service via TRUC Mempool Reorganization Bug
TL;DR
- Severity: High — mining nodes can be rendered unable to produce valid blocks after a chain reorganization
- Impact: Denial-of-service on individual miners; no fund loss, but mining operations halt until node restart
- Affected: Bitcoin Core versions 28.0 through 29.1
- Root cause: Flawed sibling-eviction logic in the TRUC (BIP 431) mempool policy
- Action: Upgrade to Bitcoin Core 28.3 or 29.2 immediately; monitor for reorg events
Overview
On November 10, 2026, the Bitcoin Core project published a security advisory for CVE-2025-62861, a High severity vulnerability patched in October 2025. The flaw sits inside the mempool policy logic that governs Topologically Restricted Until Confirmation (TRUC) transactions — a rule set introduced under BIP 431 to support Lightning Network fee-bumping strategies.
When a blockchain reorganization occurs, the buggy sibling-eviction code can leave orphaned child transactions resident in the mempool. The node then attempts to build a block template referencing transactions whose parents no longer exist, causing block construction to fail completely. The miner is effectively stuck until a full node restart clears the corrupted mempool state.
While no attacker can steal funds or rewrite history, the availability impact is real: any miner running an affected version who experiences a reorg during a volatile price window loses block-production capability with no built-in recovery. For a network where block rewards represent the primary revenue stream, even a short stall can be costly.
Technical Details
The vulnerability resides in the sibling-eviction logic that was added to handle TRUC transaction replacements during chain reorganizations. TRUC transactions impose topological ordering constraints — certain child transactions cannot be confirmed until their parents are confirmed. The eviction mechanism was designed to purge conflicting transaction sets from the mempool when a reorg invalidates a chain tip.
The bug: when a parent transaction is evicted, the code fails to consistently remove or re-evaluate its dependent child transactions. Children that should have been evicted remain in the mempool, referencing a parent that is no longer part of the active chain. The block template assembler then includes these dangling children, producing an invalid template that cannot be mined.
Key facts:
- Mechanism: Mempool state corruption via inconsistent transaction eviction
- Trigger: Blockchain reorganization (chain tip replacement)
- Exploitability: Requires a reorg event; no remote code execution or authentication bypass
- Exploit code: No public proof-of-concept exists
- Active exploitation: None reported in the wild
The fix (commit 33504) ensures that parent eviction cascades correctly to all dependent children, preventing orphaned transactions from persisting in the mempool after a reorg.
Severity & Impact
| Dimension | Assessment |
|---|---|
| Severity | High |
| Confidentiality | None — no data exposure |
| Integrity | None — no chain manipulation |
| Availability | Severe — mining node stalls until manual restart |
| Exploit complexity | Low — reorg events occur naturally on the network |
| Privileges required | None — attacker need only wait for a reorg |
| Impact radius | Individual node; no network-wide consensus failure |
The High severity reflects the combination of easy trigger conditions (reorganizations happen routinely) and the complete loss of block-production capability on affected nodes. However, the lack of a remote attack vector and the absence of fund loss keep this below Critical.
For key indicators, exploit activity over time, and detailed signal data, see the CVE-2025-62861 page.
Affected Products
- Bitcoin Core 28.0 – 28.2
- Bitcoin Core 29.0 – 29.1
The fix was backported to maintenance branches as version 28.3 and 29.2. For the full list of affected products and versions, see the CVE-2025-62861 page.
Actionable Insights
What Defenders Should Monitor
- Reorg events on your node. Check
getblockchaininfoforchainforkor unexpectedheightchanges. A reorg that coincides with a stuck mempool is the primary indicator. - Mempool size anomalies. After a reorg, if
getmempoolinfoshows transactions that reference non-existent parents, you are likely affected. - Block template failures. If
getblocktemplatereturns an error after a reorg, the node is exhibiting the failure mode described in this CVE. - Version inventory. Audit all running Bitcoin Core instances — mining nodes, full nodes, and lightwallet backends — for versions in the 28.0–29.1 range.
Why This Matters Now
The patch has been available since October 2025, but the coordinated disclosure only happened in November 2026. This means there is a ~13-month window during which unpatched nodes were fully exposed. Any miner who did not apply the backport during that period and experienced a reorg was potentially impacted. With Bitcoin price volatility, reorg events are not rare — and each one is an availability trigger.
Remediation & Mitigation
- Upgrade immediately. Deploy Bitcoin Core 28.3 (maintenance branch) or 29.2 (release branch) to all nodes. These versions contain the corrected sibling-eviction logic.
- Restart affected nodes. If a node running an affected version experienced a reorg and appears stuck, a full restart will clear the corrupted mempool state. Verify with
getmempoolinfothat no orphaned transactions remain. - Monitor chain health. Set up alerts for reorg depth and frequency. A reorg of two or more blocks should trigger an immediate node health check.
- Apply defense in depth. Run nodes on a robust infrastructure with automated restart capabilities so that a stuck node recovers without manual intervention.
- Verify patch integrity. Confirm the running version with
getblockchaininfoand validate the binary against the project's signature before deployment.
References
- CVE-2025-62861 Official Advisory
- CVE-2025-62861 Security Advisories
- CVE-2025-62861 — VulnSocial Intelligence Page
- VulnSocial
Bottom Line
CVE-2025-62861 is a High severity availability bug in Bitcoin Core's TRUC mempool eviction logic. It turns routine chain reorganizations into a mining halt on unpatched nodes. The patch has been available since October 2025 — upgrade to 28.3 or 29.2 now, verify your inventory, and monitor for reorg events.
#CVE202562861 #CVE #BitcoinCore #HighSeverity #Mempool #Mining #BIP431 #TRUC #BlockchainSecurity #DeFiSecurity #CryptoSecurity #VulnSocial
