Skip to main content
VulnerabilityPublished

CVE-2024-52916: Bitcoin Core · Unthrottled Resource Allocation

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in 0.15.0 : patch affected systems soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.15.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-52916, organizations should upgrade all Bitcoin Core nodes to version 0.15.0 or later, where the vulnerability has been addressed. In addition to patching, network-level controls can help reduce exposure by limiting incoming connections to trusted peers and implementing rate limiting on header messages to prevent flooding. Monitoring node resource usage and network traffic patterns can provide early detection of abnormal header floods. Deploying intrusion detection systems (IDS) with signatures or heuristics for unusual Bitcoin header traffic can aid in identifying exploitation attempts. For critical infrastructure, consider running nodes in isolated environments with resource limits to contain potential memory exhaustion. Regularly auditing and updating node software and dependencies is essential to maintain security posture. Finally, educating operational teams about this vulnerability and its impact will help ensure timely response and remediation.

Description

Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers.

References

Community reviews

Loading reviews…