Lifestyle

Bitcoin Core Discloses Three Patched Bugs: The Most Serious Could Have Stopped Miners From Building Block Templates

Decrypt reports that Bitcoin Core, the software behind most Bitcoin nodes, has disclosed three security flaws that are now fixed. The most serious could leave a miner's node unable to assemble new blocks until it is restarted. All three are denial-of-service and privacy issues, not coin theft, and no exploitation was reported. Node operators are generally advised to run the latest version.

About 4 min read

Bitcoin Core Discloses Three Patched Bugs: The Most Serious Could Have Stopped Miners From Building Block Templates
Image: Mokaair (Original editorial artwork)

What happened

Decrypt reports that Bitcoin Core developers disclosed three security vulnerabilities. Bitcoin Core is the reference software behind most nodes on the Bitcoin network. Nodes are the computers that run Bitcoin software and store and relay transaction and block data. One of the bugs is high severity and could disrupt mining; all three are now fixed.

Decrypt notes the flaws are denial-of-service issues (attacks that stop a system from working normally) and privacy issues, not the kind that let attackers steal coins or forge bitcoin. Also per Decrypt, Bitcoin Core grades vulnerabilities on a four-level scale from "low" to "critical", and these three fall in the middle of that range.

The three vulnerabilities compared

The table uses a few terms. A chain reorganization is when the network switches to a different chain of blocks, replacing recent blocks. A compact block is a condensed format nodes use to relay new blocks. Witness data is the signature data in a transaction used to verify it; Decrypt describes manipulating it as "a form of transaction malleation". Tor is an anonymity network. "Whitelist" permission is a trust permission that lets a connection bypass some protections.

Three Bitcoin Core vulnerabilities, compiled from Decrypt's report
IDIssue summary (per Decrypt)Possible impact
CVE-2025-62861A chain reorganization could wrongly evict some transactions, corrupting the node's mempoolAffected nodes cannot build block templates until restarted, halting miners' work of assembling new blocks
CVE-2025-62859A peer announces a compact block with manipulated witness dataCould stall the node's block processing
CVE-2025-62860Inbound connections over Tor wrongly granted "whitelist" permissionRemoves some denial-of-service and privacy protections on affected nodes

The most serious bug: why it matters to miners

Per Decrypt, the most serious bug, CVE-2025-62861, concerns block template creation. This is the process miners rely on to assemble new blocks. According to the advisory, a chain reorganization could wrongly evict certain transactions and corrupt the node's mempool (its waiting area for unconfirmed transactions). Affected nodes would then be unable to build block templates until restarted. For a miner, that means a halt to the work that earns block rewards.

Decrypt also notes that none of the three reaches the critical level, which Bitcoin Core reserves for bugs that threaten "coin theft at the protocol level, unauthorized coin creation or permanent network-wide chain splits". The developers reported no evidence the bugs were exploited.

Background: AI and vulnerability disclosure policy

Decrypt says Bitcoin Core recently rewrote its security policy to account for AI, adding a category for "easily discoverable" vulnerabilities. These are bugs that can be surfaced through a simple AI prompt, and they are now patched and disclosed immediately rather than held under a long embargo (delayed public disclosure). Decrypt also mentions a volunteer group, the "Bitcoin Red Team", that is racing to find AI-discoverable bugs across the ecosystem before attackers can exploit them.

Frequently asked questions

Could these bugs get anyone's bitcoin stolen?

Per Decrypt, all three are denial-of-service and privacy issues, not flaws that let attackers steal coins or forge bitcoin, and developers reported no evidence of exploitation.

Which vulnerability is the most serious?

Decrypt points to CVE-2025-62861: a chain reorganization could corrupt a node's mempool, leaving affected nodes unable to build block templates until restarted.

Have the bugs been fixed?

Yes. Decrypt reports all three are fixed, with the fixes shipped before the advisories were published.

What do I need to do?

Per Decrypt, the general advice is for people running nodes to use the latest Bitcoin Core software to stay protected.

Browse the latest news in this topic

Sources

Lifestyle