Bitcoin Core Patch Fixes Block Delay Flaw
Medium-severity bug CVE-2025-62859 can repeatedly stall block processing on affected nodes, and fixes ship in versions 29.2 and 30.0.
Updated on Nov. 11, 2026 in Cybersecurity

Bitcoin Core disclosed vulnerability CVE-2025-62859 on November 10, rated medium severity, which can repeatedly delay block processing on affected nodes. Versions 29.2 and 30.0 contain fixes for the flaw, which affected versions before those releases.
Why it matters
Because each failed block request forces a 10-minute wait, a node could be held back from processing valid blocks for extended periods. The issue matters to node operators worldwide who rely on timely block validation for the network's security and operation.
The flaw lets a malicious peer alter witness data in a compact block, causing a vulnerable node to clear its download state before checking the data. Each failed block request triggers a 10-minute wait, and the delay can recur indefinitely if an attacker controls all three of a target's high-bandwidth peers or the node runs with the -blocksonly option.
The players
Bitcoin Core
Bitcoin Core is the reference software implementation maintained by a open-source developer community and used by many nodes on the Bitcoin network.
Eugene Siegel
Eugene Siegel is the security researcher credited with discovering the flaw and reporting it through responsible disclosure.
The details
Eugene Siegel discovered the flaw and disclosed it responsibly. After a validation failure, the vulnerable node requests the full block from the same malicious peer and waits for a timeout, which is how the delay repeats.
Timeline
November 10, 2026: Bitcoin Core discloses vulnerability CVE-2025-62859.
Tech Race
The disclosure follows Bitcoin Core's established practice of privately reporting flaws and shipping fixes in numbered releases, here 29.2 and 30.0. It shows how peer-to-peer block relay logic remains a focus of security review as node software matures.
Operators of Bitcoin nodes should upgrade to versions 29.2 or 30.0 to remove the block-delay exposure. Users running nodes with the -blocksonly option face the indefinite-delay condition described in the disclosure and should prioritize the update.
The takeaway
Keeping node software current is the most direct defense against block-processing delays of this kind. Operators should check their running version and confirm it is 29.2 or 30.0 or later.
Further reading
For more on how software flaws like this are tracked and handled, explore our Cybersecurity coverage.







