CVE-2024-52914: Bitcoin Core · Unthrottled Resource Allocation
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 0.18.0 : patch Bitcoin Core soon.
Data as of 26 Oct 2026, 14:05 UTC
- 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.
- Affects
- Bitcoin Core before 0.18.0
- Patch
- Available – fixed in 0.18.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-52914, organizations should upgrade all Bitcoin Core nodes to version 0.18.0 or later, where the vulnerability has been addressed. If immediate upgrading is not feasible, network-level controls can be implemented to limit or filter suspicious transaction traffic, particularly from untrusted peers, to reduce exposure to crafted orphan transactions. Monitoring node logs and performance metrics for unusual delays or stalls can help detect exploitation attempts early. Implementing resource limits or throttling on orphan transaction processing, if configurable, can also reduce risk. Network segmentation and firewall rules restricting inbound peer connections to trusted nodes can minimize attack surface. Regularly reviewing Bitcoin Core release notes and security advisories ensures timely awareness of vulnerabilities and patches. Finally, participating in Bitcoin network health monitoring initiatives can provide early warnings of widespread exploitation attempts.
Description
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction.