Bitcoin Core Fixes AI-Found Bugs That Could Crash Nodes on Windows and macOS
Three vulnerabilities from an AI-assisted code scan are now public after fixes shipped, including one that could crash nodes by exhausting memory.
Key Takeaways
- Bitcoin Core published three security bugs found by an AI-assisted code scan on October 29.
- One bug could crash nodes on Windows, macOS and BSD by exhausting memory.
- All three bugs were fixed before the details went public.
- The disclosures are the first under Bitcoin Core's new policy for bugs that AI tools can rediscover.
Bitcoin (BTC) Core published three security bugs found by an AI-assisted code scan on October 29, including one that could crash nodes on Windows, macOS and BSD. All three were fixed before the details went public.
The Crash Bug
The memory bug was flagged on October 23 and confirmed the same day. It was fixed on October 27. A connected peer could keep feeding a node data until the machine ran out of memory and the node crashed, a denial-of-service flaw rather than a theft or a consensus break. A crashed node stops following the chain until it is restarted and patched. The advisory warned that on Windows and 32-bit systems the node could fail outright, and that restarting might not help until the software is upgraded.
The two other bugs came from the same automated scan, one of the first public results of developers using large language models to review Bitcoin Core code at scale. Bitcoin Core published all three together, with the fixes already shipped in point releases for the maintained versions of the software.
A Faster Disclosure Policy
The publication is the first clear exercise of Bitcoin Core's revised security advisory policy, merged on October 22. The policy adds a fast disclosure route for flaws that are easy to rediscover, on the reasoning that AI tools can find such bugs again in one prompt, so long embargoes protect nobody for long. CoinDesk described the shift when the new policy took shape, and reported the crash bug's public disclosure on October 29.
What Node Operators Should Know
The fix ships in the current point releases of Bitcoin Core, and node operators on the affected platforms need those releases to close the crash path. Node software versions are visible in any block explorer dashboard, but the authoritative list of patched releases is the project's own advisory. The Bitcoin price chart on Coinranking tracked the market through the disclosure week.
Frequently Asked Questions
What Could the Bitcoin Core Crash Bug Do?
A connected peer could feed a node data until it ran out of memory and crashed, on Windows, macOS and BSD. It was a denial-of-service flaw, not a theft bug.
When Were the Bugs Fixed?
The crash bug was flagged on October 23, confirmed the same day and fixed on October 27, before the details became public on October 29.
How Were the Bugs Found?
An AI-assisted code scan found three vulnerabilities, published under Bitcoin Core's new policy for bugs that AI tools can easily rediscover.
Sources
- AI found a way to crash bitcoin nodes on Windows and Macs. It's now public · CoinDesk
- Bitcoin Core Fixes 3 Security Bugs Discovered by AI · Bitcoinist
- Bitcoin will now stop hiding bugs an AI can find in one prompt · CoinDesk
Prices and market data: Coinranking.
