Three security flaws in Bitcoin Core: what you can do now
The Bitcoin Core project published three security advisories at once on October 28, 2026. One of them is enough to crash any node on Windows, macOS or BSD from a distance.

Table of Contents
Table of Contents
Which topics should we dive deeper into?
Select what genuinely interests you. Your picks feed directly into our editorial planning.
Crypto news that's actually worth your time.
Weekly. 60 seconds. Carefully curated by our editors: no hype, no promo flood, no spam.
Bitcoin Core published three security advisories at once on October 28, 2026. The most serious of them lets a single malicious peer crash any node running on Windows, macOS or BSD. All three points are fixed in versions 29.5, 30.4, 31.2 and 32.1. If you run your own Bitcoin node and have not updated since Monday, you are running a build whose weaknesses have been described publicly since Wednesday.
A node is the machine that verifies the entire blockchain itself instead of trusting a provider. If it goes down, no balance disappears: the keys sit in the wallet, not in the node. What is lost is your own verification, and with two of the three bugs the machine goes down with it.
Three advisories in one day: what Bitcoin Core disclosed
The three publications stand together in the project's advisory list. Two of them are rated “Medium”, one “Low”, and all three carry the note “easily discoverable”. That is the decisive rating: anyone reading the code finds the spot without particular effort.
- TCP urgent data: a peer can crash a node on Windows, macOS or BSD. Linux is not affected.
- Paused pre-BIP31 peers: a node's memory requirement grows slowly, but without a limit.
- Undo file overflow: a miner can corrupt other nodes' recovery data.
The sequence of publications is unusually tightly timed. The fixes were merged on October 26 and backported to branches 29, 30, 31 and 32. On October 27 versions 31.2 and 32.1 appeared, on October 28 followed 29.5 and 30.4, and on the same day the description of the bugs went online.
TCP urgent data: why Windows and macOS nodes crash
Bitcoin Core limits how much data it holds per peer for processing. If the queue grows too long, the software pauses reading from that socket. This mechanism is called backpressure: the software slows the peer down instead of filling up itself.
That very brake can be bypassed. On systems other than Linux, Bitcoin Core monitors network sockets with an older technique that also reacts to so-called exceptional conditions on a socket. Until now it did so even when reading had long been paused. A peer therefore only has to send TCP urgent data, a rarely used form of out-of-band transmission, and the node keeps reading. The queue grows without limit until memory is full.
The project describes the consequence in its advisory in unmistakable terms: a malicious peer can crash any connected node on Windows, macOS or BSD this way. No lead time, no preparation, no computing power. The flaw was reported on October 23 and the bug was fixed three days later.
Backpressure: the brake that fails here
Why this was possible at all comes down to a peculiarity of the implementation. On Linux, Bitcoin Core uses a different method to monitor network sockets. The faulty path simply does not exist there. Nodes on Linux servers, on most ready-made home node boxes and in data centres are therefore untouched by this point.
select() instead of poll(): Linux nodes are not affected
In practice this is the most important distinction of the whole day. Run your node on a single-board computer or a small Linux server and this bug passes you by. Run Bitcoin Core as a program on your work machine instead, meaning on Windows or on a Mac, and you belong to the affected group. The same applies to nodes on BSD systems.
The difference is not theoretical. A crashed node stops syncing, answers no queries from your own wallet and reports no incoming payments. If you run your wallet against your own node, you see an outdated balance during that time.

Pre-BIP31 peers: 2 MB of memory per hour and connection
The second bug works more slowly and is therefore more insidious. Bitcoin Core queues announcements for all peers, including those already paused. Those consist above all of the frequent notices about new transactions.
Normally that is harmless, because a peer is disconnected if it fails to answer a check message for twenty minutes. This check message is described in BIP 31, an improvement proposal from the network's early days that adds a random number to the ping message. Peers that do not support BIP 31 are exempted from this disconnection. A peer therefore only has to play old and delay reading on purpose.
Find the right exchange for your tokensThe project quantifies the growth precisely: up to 2 MB per hour and inbound connection, up to 5 MB per hour and outbound connection. A node with many inbound connections gathers enough ballast this way over days to fill up memory. Considerably less affected are nodes running with the -blocksonly setting, because there the transaction announcements that make up the bulk of the queue fall away.
This point was reported as early as September 15, 2026. A good six weeks therefore lay between report and fix, in which the flaw was known to the project and not to the public.
Undo files above 4 GiB: the third bug in the rev directory
The third point concerns a file most node operators have never heard of. Alongside the block files, Bitcoin Core writes so-called undo files, recognisable by the name pattern rev*.dat. They record which coins a block spent. The software needs these details when a reorganisation of the blockchain has to unwind a block already booked.
A reorganisation, reorg for short, is the process in which the network switches to a different, longer chain of blocks and takes back previously valid blocks. Block files are capped at 128 MiB; the undo files, by contrast, never had an upper limit. The positions inside them were stored as 32-bit numbers, and those only reach 4 GiB.
A miner can build valid blocks whose undo data is considerably larger than the blocks themselves. If an undo file grows beyond those 4 GiB, the position marker jumps back to the beginning. Newer undo data overwrites older data, and the file is truncated to the jumped-back length. If a later reorganisation unwinds an affected block, the node can no longer read its undo data and shuts down. A restart does not help. Recovery requires a complete rebuild of the index with a corrected version, a matter of hours to days on an ordinary home machine.

32-bit systems and FAT32 stay vulnerable even after the update
Here lies the point that, unlike the other two, is not fully settled. The overflow was fixed by storing the positions as 64-bit numbers and having Windows use the matching file calls. The format on disk stays unchanged, so moving the data is not necessary.
Two constellations remain exposed nonetheless. On 32-bit systems the file calls still work only up to 2 GiB, so the bug occurs there at half the data volume already, and without any reorganisation. And if your block directory sits on a FAT32 file system, for instance on an older external drive or a USB stick, you hit that format's file limit of 4 GiB. In both cases writing the undo data fails, and the node shuts down again at every start.
Exploiting the bug in practice is barely feasible on 64-bit systems. The project describes the effort in detail: the necessary transactions are not standard-compliant, an attacker would have to mine several thousand such blocks, which corresponds to roughly a month of the entire network's block production, and afterwards around eighteen further blocks of his would have to land exactly at the end of a block file on the target node. Finally he would have to win a reorganisation across two blocks. Since the file layout differs from node to node, no single preparation hits all targets.
Project Loupe: an automated scan found all three flaws
All three bugs trace back to the same source. They were found by an automated scan with a language model that runs under the name Project Loupe at Spiral and is led by Elias Rohrer. Gregory Sanders verified the findings and reported them to the Bitcoin Core security team.
Two of the three points were discovered a second time independently. Developer L0rinc reported the memory bug with paused peers on September 21 and the undo overflow on August 21, and Andrew Dorman reported the undo overflow on October 23. The fixes came from Antoine Poinsot in each case.
Find a crypto exchange with an EU licenceFrom embargo to disclosure: Bitcoin Core has changed the rules
That the descriptions stood public just one day after the finished versions is no coincidence. The project only recently changed its publication practice and gave up the long embargo period, which we reported on October 23, 2026: Bitcoin Core drops the embargo. The three advisories of October 28 are the first larger run under the new line.
For operators that has two sides. The flaws become known faster, and anyone who does not update is open to attack sooner. At the same time it is now set out in readable form what exactly can go wrong, instead of just a version number with the note “security update”.
Without your own node: where your Bitcoin balance sits then
The larger share of investors run no node of their own. Hold your coins in a software wallet on your phone or your computer and you are using other people's nodes, usually those of the wallet provider. Which wallet takes which route and where you can switch on your own verification is set out in the comparison of software wallets.
Nobody in this group is directly affected by the three bugs. A risk remains nonetheless: if the provider's node goes down, you see no current balance and get no payment confirmed. Your keys sit untouched in the wallet, and that is the whole point of self-custody.
The price did not react to the publication. Bitcoin traded at around $79,790 on the morning of October 29, 2026 (CoinGecko), about 1.6 percent below the previous day, in step with the rest of the market after the US Federal Reserve's rate decision the day before.
Bitcoin Core 32.1: stay on 32-bit and you stay vulnerable
- Check the version and switch. In the console,
bitcoin-cli getnetworkinfoshows the running version. Anything below 29.5, 30.4, 31.2 or 32.1 belongs replaced, especially on Windows and macOS. If you want to take the opportunity to separate the keys from your everyday machine, the devices are listed in the hardware wallet comparison. - Look at the file system and the architecture. If the block directory sits on FAT32 or the node runs on a 32-bit system, the third bug stays open. Moving to a modern file system removes it. If you would rather rely entirely on a provider, compare the fees in the overview of crypto exchanges.
- Watch memory consumption. If an older node's consumption grows steadily over days, that matches the second bug. With
-blocksonlythe growth turns out considerably smaller. If you prefer to keep your balance at a supervised firm, check the authorisations among the regulated crypto exchanges.
The full descriptions stand in the Bitcoin Core advisory list, and the text on the TCP flaw in the individual advisory.
(As of October 29, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
Frequently asked questions about the Bitcoin Core security flaws
Partner links: some links on this page are partner links. If you become a customer through one of them, we may earn a commission at no extra cost to you. Selection, ratings and ranking are decided independently by our editorial team. Ethics and Independence · Ownership and Funding
Transparency note: This article was produced with the assistance of artificial intelligence. Figures and claims are based on the primary sources linked in the text. The feature image was generated with AI.
For later? Save this article and find it again in your profile.
Section: All crypto hacks and scams at a glance
More on Bitcoin: All Bitcoin news at a glance
Related articles
- Bitcoin Core Tor whitelist bug: thousands of nodes treated strangers as trusted peers
- LNbits security flaw: version 1.7.0 stops thefts from Lightning wallets
- US inflation runs hot: Bitcoin at $73,600 with stops in focus before December 9
- Zcash NU7 upgrade: Zebra 7.0.0 fixes seven security flaws
- Running a Bitcoin node: is your own node worth €16 to €39 a year in electricity?
Which topics should we dive deeper into?
Select what genuinely interests you. Your picks feed directly into our editorial planning.
Crypto news that's actually worth your time.
Weekly. 60 seconds. Carefully curated by our editors: no hype, no promo flood, no spam.
November 2, 2026 8:23 AM

BTCPay Server Hack: Bitcoin Hot Wallets Drained, Shut Your Server Down Now
BTCPay Server warns of swept Bitcoin hot wallets on older installs and tells operators to shut down. What happened, who is affected and what to do now.
November 1, 2026 3:15 AM

US inflation data, Fed rate decision: Bitcoin heading into November 10
US consumer prices for October are published on November 10 at 8:30 am New York time. It is the last inflation reading before the Fed decision on December 9, and it hits leveraged positions first.
October 26, 2026 12:00 PM

Bitcoin Wallet Bug: Why Speeding Up a Payment Could Drain Your Wallet
A Bitcoin wallet bug let rogue servers swap a real payment for a fake one and trick users into signing it. How the fee bump trap works and how to stay safe.
October 25, 2026 3:31 PM

Electrum wallet vulnerable before version 4.8.3: what you can do now
Electrum released version 4.8.3 on October 23, 2026 and closed a flaw that malicious servers had already exploited. It does not harvest your keys; it targets the moment you speed up a stuck transaction.
October 23, 2026 7:34 PM

Bitcoin Core drops the embargo: “the wrong tradeoff” on easy-to-find flaws
Bitcoin Core now discloses security flaws that can be found with a simple prompt without an embargo and ships the fix for every maintained major version. What the new policy means for your node and your wallet.
October 14, 2026 7:40 PM

US inflation rises to 3.7 percent, core rate above forecast: what matters now for Bitcoin
US consumer prices rose 3.7 percent in September, and the core rate 2.6 percent. Both figures came in above forecast, two weeks before the Fed decision on October 28.
October 11, 2026 4:50 AM

90 Crypto Kidnappings and Robberies in 7 Months: Why France Is the Most Dangerous Country for Bitcoin Holders
France logged 90 crypto kidnappings, extortions and violent thefts this year, one every 2.5 days. Leaked tax data is to blame. Here is how to protect yourself.
October 10, 2026 3:39 PM

Will AI Break Bitcoin? Vitalik Says Prepare for "Bunker Mode", Hoskinson Calls It Numerology
Vitalik Buterin says AI could crack crypto's encryption within 2 years. Charles Hoskinson says that is nonsense. Who is right, and what should you do?
October 8, 2026 4:42 PM

Bitcoin and Ether Under AI Pressure: “Bunker Mode” for Holdings on Already Signed Addresses
A researcher at the Ethereum Foundation considers a break of the ECDSA signature by AI possible within months in the worst case, and advises large holders to move to addresses that have never been used. Vitalik Buterin disagrees on the pace, and Coinbase's chief cryptographer sees no evidence.
October 1, 2026 7:25 AM

US core inflation falls to 3.0 percent: what investors need to know before the Fed decision on October 28
US core inflation ran at 3.0 percent in August, clearly below the expected rate. That shifts expectations for the Fed meeting on October 28 and helps decide how much room the Bitcoin price gets in the fourth quarter.
September 30, 2026 4:14 AM

Bitcoin Price Before the Core PCE at 14:30 CEST: Will the $82,735 Level Hold?
At 14:30 CEST today the Bureau of Economic Analysis publishes the core PCE deflator for August, the inflation gauge the Fed anchors its 28 October rate decision to. Bitcoin stands at $83,329, less than $600 above its daily low, and anyone holding on leverage decides this morning.
September 27, 2026 11:28 AM

Crypto Prices Today: Bitcoin Holds $84,000 After Its Best Week Since January
Bitcoin at $84,600, ETH at $2,700, NEAR up 56 percent on the week. Crypto prices today, what drove the rally, and what could move the market next.
September 17, 2026 10:40 AM

Crypto News Today: Bitcoin Holds $76,000 After Fed Hike and CLARITY Act Collapse
The CLARITY Act died in the Senate, the Fed hiked for the first time since 2023, and Zcash ripped anyway. Here is the full crypto market update.
September 17, 2026 1:12 AM

Securing BTCPay Server: Why Updating to 2.4.4 Alone Does Not Protect Your Lightning Node
The project behind BTCPay Server reports that bots are probing payment servers whose Lightning interface was exposed by hand. The update to 2.4.4 closes the public default route; a reverse proxy rule you built yourself it does not clear away.
September 16, 2026 7:12 PM

Borrowing Against Bitcoin Instead of Selling: When German Tax Still Applies
Posting Bitcoin as collateral for a loan is not a sale in Germany, because section 39 of the Fiscal Code keeps the coins attributed to you for tax purposes. Tax arises only when the collateral is liquidated, and then the one thing that decides the bill is how long you held the coins beforehand.
September 15, 2026 10:36 AM

Bitcoin Core 32.0 Arrives October 10: How to Check Whether Your Node Falls Out of Maintenance
The first release candidate for Bitcoin Core 32.0 has been out since September 14, with the release planned for October 10. With it, the 29 series loses its security updates - and our own count shows that affects 60 percent of reachable nodes.
September 15, 2026 10:25 AM

Updated Core Lightning via Docker? How to Check the Security Fix Is Really There
Your node reports v26.06.7 at startup and the security fixes can still be missing: four Docker tags served images with the right number and the wrong content in late August. Here is how to check your Lightning node's digest and catch up cleanly.
September 12, 2026 1:12 PM

Crypto ETN in Your Portfolio: How to Check Who Really Owes You the Bitcoin
A Bitcoin ETN is legally a debt security, not a fund unit. We counted the 122 crypto ETNs tradable on Xetra ourselves and show you the three details worth checking before you buy.
September 11, 2026 1:26 PM

Alby Hub Security Flaw: How to Check Whether Your Bitcoin Lightning Node Is Reachable From the Internet
Alby confirmed a critical flaw in Alby Hub v1.7.0 through v1.18.5 on September 9, 2026; it is only exploitable if the management interface sits openly on the internet. What to check on your node, why the fix is a good twelve months older than the warning, and which step comes before the update.
September 9, 2026 4:20 AM

XRP Ledger Amendment of September 11: What Wallet, Node and AMM Users Should Know About fixCleanup3_3_0
Recap as of September 27, 2026: the amendment fixCleanup3_3_0 was due to activate on the XRP Ledger on September 11, 2026 at 11:15 UTC. Our own query on September 27 shows it as enabled. This article describes the situation before that date and who had to act on their wallet, node or AMM position.
September 7, 2026 6:05 PM

Crypto News Today: Bitcoin Holds $79,000 While The Fed, Tether And A Hacker All Make Trouble
Bitcoin is pinned below $80,000 as September hike odds sit at 58%. Plus a warning on Tether's keys and the Coldcard attacker moving funds again.
September 2, 2026 1:47 PM

Pi Network Protocol 27 on September 15: What Our Measurement on Mainnet and Testnet Shows
The Pi mainnet is on protocol 26 on September 2, the first testnet on 27, the second still on 26. We dated all seven protocol jumps of the past five months to the exact ledger and show what node operators and holders can read from them.
September 1, 2026 12:19 PM

Von der Leyen Wants Your Bank Deposits: Here Is How to Keep Control of Them
Brussels wants Europe's 10 trillion euros in deposits funding its companies. What it means for savers, and why Bitcoin savings plans matter.
August 30, 2026 10:23 PM

Core Lightning Security Vulnerability: What Node Operators Must Do Now
Core Lightning has reported several confirmed security vulnerabilities and shipped an emergency update as version 26.06.7. If you run your own Lightning node, update now or restart it with the --offline switch.
August 22, 2026 4:34 PM

BitBox02: Firmware 9.26.5 Closes Three Security Vulnerabilities. What to Check Now
BitBox released firmware 9.26.5 on August 17, 2026, closing three security vulnerabilities in the BitBox02 and BitBox02 Nova. Existing seeds are not affected according to the manufacturer; an update is due anyway, and with unused devices the order matters.
More from CryptoTicker


