The flaws identified include: TCP urgent data crashes on non-Linux systems, paused pre-BIP31 peers causing unbounded memory growth, and undo file overflow in rev*.dat that could trigger node shutdown after reorgs.

Bitcoin Core’s advisory descriptions are available on the project’s site, and the AI-assisted article has been fact-checked.

Fixes were merged on October 26 and backported to branches 29, 30, 31, and 32; updated versions are 29.5, 30.4, 31.2, and 32.1.

Operators should verify node versions (29.5+, 30.4+, 31.2+, or 32.1+), inspect filesystem and architecture (avoid FAT32 and 32-bit where possible), and monitor memory usage, especially with -blocksonly settings.

Bitcoin Core published three security advisories on October 28, 2026, including one that can crash any node on Windows, macOS, or BSD due to a malicious peer.

Project Loupe, an automated scan by Spiral, detected all three flaws, with independent confirmations for two of them.

For non-node holders, risk is indirect: provider node outages can lead to outdated balances or failed payments; self-custody remains essential.

Bitcoin Core moved from embargoed disclosures to public advisories, increasing transparency but also risk exposure for unpatched nodes.

Windows, macOS, and BSD users are at risk due to older backpressure handling, while Linux nodes remain largely unaffected by the first flaw.

Market context notes Bitcoin around $79,790 on Oct 29, 2026, with broader moves linked to Federal Reserve decisions.

The third flaw involves undo files exceeding 4 GiB, which can shut down a node; 32-bit systems and FAT32 file systems remain vulnerable after updates.

The second flaw can drive memory usage up to about 2 MB/hour per inbound peer and 5 MB/hour per outbound peer, risking memory exhaustion over time.