Bitcoin Core disclosed three node vulnerabilities on October 28, 2026, after releasing fixes in versions 29.5, 30.4, 31.2, and 32.1. The most immediately exploitable issue allowed a malicious peer to exhaust memory and crash a connected Bitcoin Core node on Windows, macOS, or BSD, making the update directly relevant to network operators even though Linux nodes were not affected by that flaw.
The medium-severity bug arose in the select()-based socket path used outside Linux. A peer could send TCP urgent data to bypass Bitcoin Core’s backpressure mechanism, continue adding data to a paused processing queue without a limit, and eventually terminate the node through memory exhaustion.
A second flaw caused slower unbounded memory growth when paused peers using the pre-BIP31 protocol continued sending announcements. Bitcoin Core estimated growth of up to 2 MB per hour for each inbound peer and 5 MB per hour for each outbound peer, with nodes running -blocksonly less exposed because transaction announcements represented most queued messages.
The third, low-severity flaw involved 32-bit positions in undo files. Under extreme and impractical conditions, a miner could corrupt undo data and cause shutdowns during a precisely constructed reorganization, or when affected blocks were connected on Windows and 32-bit systems. The fixed releases address 64-bit systems, but 32-bit installations and nodes storing block data on FAT32 remain affected.
The first two reports came from an automated language-model scan conducted through Spiral’s Project Loupe and were validated before coordinated fixes. The disclosures do not describe a Bitcoin consensus failure, loss of BTC, or a confirmed network-wide outage. Readers following the live BTC price should distinguish an implementation-level node risk from a change in Bitcoin supply or transaction validity.
Operators should verify their installed version and storage environment rather than assuming the latest major branch alone is sufficient. The next measurable signals are adoption of 29.5, 30.4, 31.2, and 32.1 among reachable nodes, any reports of attempted exploitation, and additional guidance for 32-bit or FAT32 deployments that remain outside the complete fix.
Sources
- Bitcoin Core advisory: TCP urgent-data memory exhaustion, October 28, 2026.
- Bitcoin Core advisory: paused-peer memory growth, October 28, 2026.
- Bitcoin Core advisory: undo-file overflow, October 28, 2026.
- Bitcoin Core 32.1 release notes.
- CoinDesk, October 29, 2026.
Information disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Crypto assets are volatile, and readers should conduct their own research.
