For 18 Months, Any Miner Could Have Crashed Bitcoin's Network. 43% of Nodes Still Haven't Patched.

For eighteen months, a bug sat inside Bitcoin Core that let miners remotely crash any node on the network. The fix was shipped without a word — buried inside a commit titled “Improve parallel script validation error debug logging.” Today, 43% of Bitcoin nodes are still running the vulnerable code.

Bitcoin Core disclosed CVE-2024-52911 on May 5, 2026 — a high-severity memory safety vulnerability that affected every version from 0.14.0 through 28.x. That covers nearly a decade of releases.

The short version: a malicious miner could have constructed a specially crafted invalid block and used it to crash any unpatched full node they wanted. And because it’s a use-after-free bug, remote code execution — while considered unlikely — couldn’t be ruled out.

How the Bug Actually Worked

Bitcoin Core pre-calculates and caches signature validation data during block processing, then hands that work off to background threads. The vulnerability? For certain invalid blocks, that cached data could be freed from memory while a background validation thread was still reading it.

The result is a classic use-after-free: the software keeps reading from memory that’s already been destroyed. In the best case, the node crashes. In the worst case, an attacker controls what ends up in that freed memory region and executes arbitrary code on your machine.

This is Bitcoin Core’s first disclosed memory safety bug. The codebase is written in C++ — a language notorious for this class of vulnerability — and the fact that this kind of bug survived for this long in one of the most scrutinized codebases in open-source history should give everyone a moment of pause.

The Covert Fix

Cory Fields of MIT’s Digital Currency Initiative found the vulnerability on November 2, 2024, and privately reported it to Bitcoin Core developers. Four days later, Pieter Wuille had a fix ready. Rather than flag it as a security patch — which would have telegraphed the bug’s existence to anyone watching the repo — the PR was titled “Improve parallel script validation error debug logging.”

The fix was merged on December 3, 2024, and shipped publicly with Bitcoin Core v29.0 in April 2025. Public disclosure was intentionally delayed until 28.x reached its end-of-life on April 19, 2026 — the standard Bitcoin Core responsible disclosure protocol.

That means the fix was in the wild for over a year before anyone outside the core dev team knew what it was actually fixing.

43% of the Network Is Still Exposed

Here’s the problem: Bitcoin Core doesn’t auto-update. Every node operator has to upgrade manually. And based on data from Clark Moody’s Bitcoin dashboard, roughly 43% of active Bitcoin nodes are still running versions older than v29.0.

Those nodes remain vulnerable to CVE-2024-52911 right now.

The saving grace is economics. To exploit this bug, an attacker would need to mine an invalid block with enough proof-of-work to get it accepted — but invalid blocks don’t pay out block rewards. You’d burn real hashpower for nothing but the ability to crash some nodes. That’s a terrible trade, which is likely why nobody exploited this in the wild during the 18 months it sat unpatched.

But “economically disincentivized” is not the same as “impossible.” A nation-state actor, a well-funded adversary, or someone with access to cheap hashpower (hello, large mining pools) could run this attack at manageable cost if they wanted to cause disruption rather than make money.

This Is Bitcoin’s Dirty Secret About Decentralization

Bitcoin’s ethos celebrates running your own node. Don’t trust, verify. But the flip side of that principle is that nobody can force you to upgrade. There’s no auto-update mechanism. There’s no kill switch. There’s just a changelog and a GitHub release page that most node operators never read.

The result: nearly half the network sitting on a known critical vulnerability for over a year after the patch shipped, and longer still since discovery.

This isn’t the first time this has happened. Bitcoin Core’s security disclosure page is a graveyard of bugs that lingered unpatched on significant portions of the network for months or years. Decentralization is a feature — until it means you can’t push a security update.

Why This Matters for Crypto Jobs

The Bitcoin Core security pipeline just got a lot more visible. Here’s what this disclosure shakes loose for the job market:

Bitcoin infrastructure developers are in demand. The core team caught and quietly fixed this bug efficiently — but the 43% unpatched rate shows the ecosystem desperately needs more people focused on node operator outreach, DevOps tooling, and upgrade automation. If you’re a C++ developer, there’s a direct path into Bitcoin Core contribution.

Security researchers are having a moment. Cory Fields found this bug. Pieter Wuille fixed it in four days. These are the kinds of people every Layer 1 protocol, exchange, and custodian is scrambling to hire. If you have a background in memory safety, fuzzing, or low-level systems security, the crypto industry needs you more than ever.

Node operators and infrastructure teams are getting scrutiny. Exchanges, Lightning node operators, payment processors — any business running Bitcoin infrastructure is now getting audited by their security teams. That creates demand for Bitcoin Core expertise, upgrade tooling, and security consulting.

The narrative around “Bitcoin is unassailable” just took a hit. That’s actually bullish for security-focused builders. Every time a high-profile vulnerability comes out, investment in protocol security and auditing firms follows. Watch for job postings at firms like Trail of Bits, Halborn, and Coinspect to spike in the coming weeks.

If you’re a developer thinking about where to focus: Bitcoin infrastructure security is one of the most impactful, underbuilt areas in the entire industry. The demand is real, the work is hard, and the stakes are as high as they get.

---

Looking for your next role in crypto security, Bitcoin infrastructure, or blockchain engineering? Browse hundreds of verified Web3 jobs — from Core protocol work to smart contract auditing — at cryptogrind.com. New positions added daily.