The vulnerability is an out‑of‑memory condition that can be triggered when Bitcoin Core processes data that exhausts available memory, causing the node to crash or become unresponsive. The fallout is a loss of service availability for the affected node, potentially affecting its peers and the broader network, though no confidentiality or integrity breaches are described. The weakness is a classic uncontrolled resource allocation problem.

Bitcoin Core software versions prior to 29.5, 30.4, 31.2, and 32.1 are impacted. Any instance running those releases is at risk.

No EPSS or CVSS scores are supplied, and the vulnerability is not listed in the CISA KEV catalog. Because the issue involves memory exhaustion, it can potentially be triggered remotely by an attacker sending crafted data or excessive traffic to a vulnerable node. The lack of exploitation statistics suggests a moderate risk that should be treated as a serious denial of service threat until mitigated.