The Bitcoin Buzz

‹ All Posts

Bitcoin Core Publishes AI-Discovered Node Bugs After Shipping Fixes Across Supported Releases

Bitcoin Core Publishes AI-Discovered Node Bugs After Shipping Fixes Across Supported Releases

Bitcoin Core has published details of three vulnerabilities discovered through an automated large-language-model scan, pairing an unusually direct disclosure with patches already released for supported versions. The most immediate issue affects Windows, macOS, and BSD nodes: a malicious connected peer could use TCP urgent data to bypass a backpressure mechanism, queue unbounded work, and crash the node through memory exhaustion.

Bitcoin Core’s technical disclosure says Project Loupe, an automated LLM scan run through Spiral, identified that issue on October 23. Gregory Sanders validated and forwarded the report to the project’s security team the same day. A fix was merged and backported on October 26; Core 31.2 and 32.1 shipped with the fix on October 27, followed by versions 29.5 and 30.4 on October 28, when the project disclosed the vulnerability publicly. Primary source: https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/

The disclosure comes after Bitcoin Core changed how it treats flaws considered easy to rediscover. Rather than retaining them under the project’s normal delayed-publication schedule, it now plans to disclose such issues once fixes are available across maintained versions. Bitcoin Core 32.1 notes that three medium- and high-severity vulnerabilities fixed in version 30.0 remain under the regular schedule and are expected to be disclosed in two weeks. Release notes: https://bitcoincore.org/en/releases/32.1/

Two further issues revealed this week reinforce why the change matters. One allowed memory use to grow slowly for paused pre-BIP31 peers, at rates the project estimates could reach 2 MB per hour per inbound peer and 5 MB per hour per outbound peer. The fixes arrived in 31.2 and 32.1 on October 27, then in 29.5 and 30.4 the next day. The project says nodes running with -blocksonly are much less affected because transaction announcements account for most queued messages. Details: https://bitcoincore.org/en/2026/10/28/disclose-fpausesend-oom/

A third, low-severity bug concerned undo files. Under highly unusual conditions, a miner could make undo data exceed a 32-bit file-position limit and cause affected nodes to shut down during a precisely shaped reorganization. Core calls exploitation impractical, but notes that 32-bit systems and nodes using FAT32 remain affected. Disclosure: https://bitcoincore.org/en/2026/10/28/disclose-undo-overflow/

The episode is not a change to Bitcoin’s consensus rules. It is a maintenance and operational-security event for people who run the software that validates and relays the network. The key fact is sequence: human contributors verified the automated findings, fixes were distributed first, and the technical details followed after patched releases were available.

← Back to The Bitcoin Buzz