Thursday, November 19, 2026

Bitcoin Core Discloses Compact Block Processing Vulnerability

Bitcoin node rack with a block diagram fading to a stall icon and a looming malicious peer.

Bitcoin Core Discloses Compact Block Processing Vulnerability

Bitcoin Core has publicly disclosed CVE-2025-62859, a medium-severity peer-to-peer vulnerability that can allow a malicious node to delay block processing through malformed compact block data. According to Bitcoin Core’s official November 10 security disclosure, the flaw affects software without the fix shipped in versions 30.0 and 29.2 and can force a victim node into a 10-minute block-download timeout under specific conditions.

The vulnerability is not newly patched. Security researcher Eugene Siegel privately reported it on April 28, 2025, Gregory Sanders opened the corrective pull request the following month, and the change merged in June. Bitcoin Core 30.0 shipped with the fix on October 10, 2025, followed by 29.2 on October 14. The technical details remained private for more than a year under Bitcoin Core’s coordinated vulnerability-disclosure process.

Compact Block State Creates a 10-Minute Stall

Bitcoin Core uses compact blocks to reduce the bandwidth required to propagate new blocks between nodes. Rather than transmitting every transaction in full, peers can reconstruct much of an announced block from transactions they already possess. The vulnerability appeared in the sequence used to validate that reconstructed block. Affected versions cleared the block’s download state before checking whether its witness data had been maliciously modified.

If that witness-malleation check failed, Bitcoin Core fell back to requesting the complete block using GETDATA. The problem was that it asked the same peer responsible for the malformed compact block and then waited for a timeout of up to 10 minutes. An attacker that announced the compact block first could therefore deliberately move a victim from rapid reconstruction into a substantially slower fallback path.

The attack becomes more persistent under narrower networking conditions. Bitcoin Core says an adversary controlling all three of a victim’s high-bandwidth compact-block peers could repeat the stall indefinitely. The same applies to nodes operating with -blocksonly, a configuration that changes how transactions are relayed and how compact blocks can be reconstructed. The weakness affects the victim node’s ability to remain synchronized promptly rather than changing Bitcoin’s underlying consensus rules.

The fix moves the witness-mutation check into FillBlock, preventing the vulnerable state transition during compact-block reconstruction. Bitcoin Core 29.2 explicitly lists the change as p2p: Add witness mutation check inside FillBlock. Correcting where the validation occurs prevents the malicious peer from forcing the same 10-minute fallback sequence through this mechanism.

Disclosure Arrives After Vulnerable Branch Reaches EOL

The delayed publication follows Bitcoin Core’s standard security policy. Medium- and high-severity vulnerabilities that are not classified as easily discoverable are normally disclosed after the last affected release reaches end-of-life. The 29.x series reached that point on October 27, 2026. The timing reflects an intentional embargo designed to give node operators time to adopt patched software before exploit details become public.

That process was recently modified for vulnerabilities that automated tools or other techniques can rediscover with minimal effort. Bitcoin Core now allows those issues to receive accelerated public disclosure alongside patched releases, rather than preserving the longer severity-based embargo. CVE-2025-62859 followed the standard disclosure path, with the patch circulating long before its attack mechanics became public.

The issue also differs from a recent Bitcoin Core PSBT signing vulnerability, which concerned what transaction outputs a wallet signature committed to rather than peer-to-peer block propagation. Other Bitcoin security discussions, including proposed quantum-attack countermeasures, address still different cryptographic threat models. CVE-2025-62859 is specifically a node-availability weakness in compact-block handling, not a wallet-key or cryptographic compromise.

Bitcoin Core now maintains newer branches while 29.x is unsupported. For node operators, the disclosure reinforces that point releases can contain security fixes whose significance is intentionally not made public until much later. Running maintained software therefore protects against some known-but-embargoed vulnerabilities before users have enough public information to evaluate those vulnerabilities themselves.

Satoshipick
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.