Bitcoin Node Flaw Lets Peers Stall Block Processing
Patched in Bitcoin Core 29.2 and 30.0, the medium-severity bug shows that block-relay code remains a live attack surface.
Updated on Nov. 12, 2026 in Cybersecurity

Bitcoin Core, the reference software for the Bitcoin network, disclosed vulnerability CVE-2025-62859 on November 10, 2026. The flaw is rated medium severity and is fixed in Bitcoin Core 29.2 and 30.0; the development is shipped as a patch release, not a research-stage finding.
Why it matters
The bug lets a malicious peer stall block processing on a vulnerable node, showing that block-relay logic remains an attack surface even in mature software. Its discovery and responsible disclosure by an independent researcher reflects how open-source blockchain infrastructure is being hardened through coordinated disclosure.
The disclosure rests on a specific measured delay: a 10-minute timeout triggered each time a block request fails, which an attacker can repeat indefinitely under the conditions described. The source does not report exploitation data or the number of affected nodes.
The players
Bitcoin Core
The open-source reference implementation of the Bitcoin protocol, maintained by a community of contributors, whose releases define the software most Bitcoin nodes run.
Eugene Siegel
The researcher credited with discovering the flaw and disclosing it responsibly to the Bitcoin Core project.
The details
Bitcoin nodes use compact blocks, a bandwidth-saving format that sends a summary of a block and lets the receiving node fill in the transactions it already has. In the flawed code, a malicious peer alters the witness data, which is the signature material attached to transactions, inside a compact block. The vulnerable node clears its download state before checking that data, then requests the full block from the same peer and waits for a timeout, so the attacker can repeat the cycle.
Timeline
November 10, 2026: Bitcoin Core discloses the vulnerability.
The Tech Race
The disclosure is a relay-layer flaw in Bitcoin Core rather than a consensus-level break, which places it in the ongoing effort to harden peer-to-peer networking as node software is maintained alongside the protocol. Competing node implementations are not addressed in the source, so the comparison is limited to Bitcoin Core's own patch history.
Operators of Bitcoin Core nodes should upgrade to version 29.2 or 30.0, which contain the fix. Users of wallets and services that rely on a vulnerable node may see delayed block processing until their software is updated.
The takeaway
Node operators running any Bitcoin Core release before 29.2 or 30.0 should upgrade now, and those running with -blocksonly should check their configuration against the disclosure. Watch for the release notes of the next Bitcoin Core maintenance release to confirm the fix's full scope.
Further reading
For broader context on how software flaws like this are found and fixed, see the Cybersecurity section.


