Skip to main content
Mallory
UnratedVulnerability

CVE-2025-62861: Bitcoin Core Mempool Inconsistency During Blockchain Reorganization

Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 6 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-62861CWE-841

CVE-2025-62861 is a high-severity transaction-processing vulnerability in Bitcoin Core versions 28.0–28.2 and 29.0–29.1. During a blockchain reorganization, incorrect application of TRUC transaction-processing rules to transactions returned from disconnected blocks can evict a parent transaction while leaving child transactions that spend its outputs in the mempool. This inconsistent state causes block templates generated by the node to fail validation, preventing mining through that node until it is restarted. No exploitation was known at disclosure.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Affected mining nodes cannot generate valid block templates after the triggering reorganization, disrupting block production until node restart. The vulnerability does not enable bitcoin theft or creation of bitcoins outside protocol rules.

Mitigation

If you can’t patch tonight, do this now.

Restart an affected node to restore mempool consistency and valid block-template generation. Restarting provides recovery but does not prevent recurrence on vulnerable versions; installing a fixed release is required for a durable remedy.

Remediation

Patch, then assume compromise.

Upgrade to a supported Bitcoin Core release containing the fix. The vulnerability was fixed in versions 28.3, 29.2, and 30.0, released in October 2025. The fix disables the related-transaction eviction mechanism when transactions are returned to the mempool following a blockchain reorganization.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-62861 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2025-62861 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-62861?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2025-62861.
Is there a patch for CVE-2025-62861?
Upgrade to a supported Bitcoin Core release containing the fix. The vulnerability was fixed in versions 28.3, 29.2, and 30.0, released in October 2025.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.