Bitcoin Core Discloses High-Risk CVE-2024-52911 Vulnerability; 43% of Nodes Remain at Risk

iconChainthink
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Bitcoin Core disclosed a high-risk vulnerability, CVE-2024-52911, affecting versions 0.14.1 through 28.4. The flaw enables miners to remotely crash nodes and execute code through specially crafted blocks. Discovered by Cory Fields in November 2024, the fix was merged in December and released in Bitcoin Core version 29 in April 2025. The 28.x series was deprecated on April 19, 2025. Approximately 43% of nodes remain unpatched, leaving them vulnerable.

ChainThink report: According to the official announcement, Bitcoin Core developers have disclosed a critical vulnerability numbered CVE-2024-52911.

The vulnerability affects versions 0.14.1 to 28.4, allowing miners to remotely crash other users' nodes and execute code by mining specially crafted blocks.

The vulnerability was discovered and privately reported by developer Cory Fields in November 2024, the fix was merged in December of that year, and it was released in April 2025 with version v29.

The last vulnerable 28.x series was discontinued on April 19. Since upgrading Bitcoin full nodes is voluntary, it is estimated that approximately 43% of nodes worldwide are still running outdated, vulnerable software and are at potential risk.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.