Bitcoin Core has revealed three security vulnerabilities discovered via AI-assisted scanning, including a bug capable of crashing Bitcoin nodes operating on Windows, macOS, or BSD through a malicious connection.
Based on security advisories published by Bitcoin Core on October 28, patches were rolled out across four software versions on October 27 and 28. These discoveries originated from Project Loupe, which utilizes a large language model to automatically review the codebase. Human volunteers verified the results before passing them along to the security team.
Bitcoin Core Fixes Bug That Could Crash Windows and Mac Nodes
The most immediate danger centered on the way Bitcoin Core processed incoming network data on operating systems other than Linux. A connected threat actor could transmit crafted data, forcing the program to keep accumulating messages past the point where standard memory thresholds should have halteding the influx.
Consequently, memory consumption could swell until the node failed. Bitcoin Core classified this vulnerability as medium severity, noting that Linux nodes remained untouched. Project Loupe flagged the issue on October 23, and contributor Gregory Sanders verified it that same day. A patch was merged by developers on October 26.
Subsequently, Bitcoin Core launched versions 31.2 and 32.1 on October 27, trailed by versions 29.5 and 30.4 on October 28, all of which incorporate the remedy. A Bitcoin node independently verifies transactions and blocks while trading data with other machines across the network.
AI Scan Uncovers Two Additional Bitcoin Core Vulnerabilities
A second medium-severity weakness permitted a connected machine to falsely claim it was utilizing a legacy Bitcoin communication protocol. By dragging out the message reading process, that peer could cause announcements to pile up in a node’s memory without triggering the standard timeout that would normally drop the connection.
Bitcoin Core said memory usage could climb by as much as 2 MB per hour for every incoming connection and 5 MB for every outgoing connection. Project Loupe flagged this problem on September 15, while developer L0rinc submitted an independent report six days afterward.
The third security gap involved files utilized by Bitcoin Core when the network replaces recent blocks with an alternate chain. A miner could forge blocks that forced these files to expand past their intended boundaries. The team categorized this vulnerability as low severity because an exploit on standard 64-bit platforms would demand thousands of uniquely engineered blocks alongside exact parameters.
Nonetheless, vulnerable Windows and 32-bit nodes could experience continuous shutdowns. Bitcoin Core cautioned that a simple reboot would fail to fix such crashes. While the newest patches safeguard supported 64-bit architectures, 32-bit hardware and nodes relying on FAT32 storage stay vulnerable.
Bitcoin Core Changes Disclosure Policy as AI Speeds Up Bug Discovery
These disclosures came on the heels of a policy shift announced by Bitcoin Core on October 22. In the past, the project held off on disclosing medium- and high-severity bugs for roughly one year following the initial patched major release to give users extra time to upgrade.
Developer Antoine Poinsot explained that language models have made certain software weaknesses much simpler to rediscover. “For these issues that are easy to find, this is the wrong tradeoff,” he stated in a message to the Bitcoin development mailing list.
Under the updated guidelines, developers deploy patches for readily discoverable flaws across all supported versions without delay and release corresponding advisories simultaneously. Other types of vulnerabilities maintain their standard disclosure timelines. Furthermore, Poinsot noted that three separate, unrelated flaws will get individual public advisories two weeks after the October 28 announcement.
ALSO READ: Nasdaq, S&P 500 Futures Gain as Chip Stocks Rally Following SK Hynix Earnings



