The vulnerability is an out‑of‑memory (OOM) condition in Bitcoin Core that can be triggered by normal or malicious traffic. When the OOM issue is activated the node consumes excessive memory until it cannot allocate further memory, leading to resource exhaustion and a potential denial of service. The impact is a loss of availability for the node, affecting both the local owner and the broader Bitcoin network if the compromised node is part of the consensus or relay infrastructure.

Bitcoin Core builds released before version 29.5, 30.4, 31.2 and 32.1 are affected. No vendor or product name is listed in the CNA data, but the references indicate this applies to the open‑source Bitcoin Core software distributed via the official project channels.

The CVSS score is not provided, and EPSS data is unavailable, so the exact likelihood of exploitation is unknown. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is remote, through specially crafted network messages or an unusually large transaction stream that forces the node to allocate more memory than it can handle. Even if exploitation is simple, the resulting denial of service could disrupt transaction validation and relay functions, making the risk significant for operators running full nodes.