# Bitcoin Core discloses a security flaw that allowed blocks to be delayed by up to ten minutes

> Bitcoin Core discloses a flaw fixed in 2025 that allowed a malicious node to delay the processing of a block by up to 10 minutes
> By Covadonga Fernandez · Bitcoin · 2026-11-11

Bitcoin Core disclosed yesterday, November 10, 2026, a security flaw that allowed a malicious node to delay the processing of a block on another node by up to ten minutes. Under certain conditions, the attacker could repeat the maneuver indefinitely. The developers fixed the vulnerability, identified as CVE-2025-62859 and classified as medium severity, in October 2025.

## When the flaw appeared

Bitcoin nodes can announce a block in compact format. This way, the receiver reconstructs the block with the transactions it already has and avoids downloading it in full. The flaw appeared when a malicious node got ahead of the others and sent a compact version with altered transaction validation data. If the check failed, Bitcoin Core requested the full block again from the same node and waited up to ten minutes to receive it.

Under certain conditions, the delay could be repeated indefinitely. According to Bitcoin Core, it was enough for the attacker to control the three nodes sending compact blocks to the receiver in high-bandwidth mode. It could also prolong the blockage if the attacked node used the blocksonly option, which limits the receipt of transactions pending confirmation. In both cases, the wait of up to ten minutes could be repeated each time the attacker got ahead of the others and announced a new manipulated compact block.

Eugene Siegel discovered the vulnerability and reported it to the Bitcoin Core security team on April 28, 2025. The project distributed the first fix on October 10 of that year with version 30.0. Four days later, it incorporated it into the previous branch with the release of version 29.2.

[Bitcoin Core](https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62859/) made the details of the flaw public on November 10, 2026, more than a year after distributing the fix. The disclosure came two weeks after support ended for the 29.x branch, the last one that included vulnerable versions.
