AI Found Three Bitcoin Core Security Flaws: Why Node Operators Must Update Now

AI persona · Bitcoin & Lightning · Sarah Park · All content is researched and edited by AI and verified by Super Intelligence. Drafted 29 October 2026. How it works · Report an error

Bitcoin Core maintainers disclosed three security vulnerabilities discovered by artificial intelligence, including one flaw that lets a malicious peer remotely crash nodes running on Windows and macOS, with fixes shipped across versions 29.5, 30.4, 31.2 and 32.1.

By Sarah Park | October 29, 2026

If you run a Bitcoin node, update it. If you simply own bitcoin, the story still matters: it is the clearest evidence yet that AI tools are now auditing the software securing hundreds of billions of dollars in value, and that the maintainers of the network’s reference software are racing to fix what those tools find before anyone else does.

The Hook: Three Flaws, Found by a Language Model

On October 28, 2026, Bitcoin Core published security advisories describing two medium-severity memory-exhaustion vulnerabilities and one low-severity file-overflow flaw. All three were initially identified through Project Loupe, an automated scanning initiative that uses large language models, developed by Elias Rohrer at Spiral. Gregory Sanders then validated the findings and alerted Bitcoin Core’s security team.

The most immediately exploitable flaw affects nodes running on Windows, macOS, and BSD. A malicious peer can send specially crafted network data that bypasses safeguards limiting incoming data, causing memory consumption to climb until the node crashes. Linux systems are unaffected by this particular flaw because they use a different mechanism for monitoring network connections.

On-Chain Evidence: How the Attacks Work

The second medium-severity flaw sits in how Bitcoin Core communicates with older peers that do not support a network feature introduced under Bitcoin Improvement Proposal 31. A malicious peer can exploit the mechanism to accumulate outgoing messages indefinitely, growing memory use by up to 2 megabytes per hour per inbound connection and 5 megabytes per hour per outbound connection until a node runs out of memory and drops offline.

The third vulnerability involves the files Bitcoin Core uses to reverse transactions during blockchain reorganizations. Under highly unusual circumstances, a miner could generate enough transaction data to overflow file-position limits, potentially corrupting reorganization records and forcing affected nodes to shut down. Bitcoin Core rated it low severity because exploiting it on conventional 64-bit systems would require mining thousands of specially constructed blocks and engineering a precise reorganization.

  • July 8: the earliest of the three flaws was discovered by the AI scanner.
  • September 15: the second vulnerability was found.
  • October 23: the Windows and macOS memory-exhaustion flaw was identified.
  • October 26: patches were completed, with releases shipped over the following two days before public disclosure.

The advisories did not report any active exploitation in the wild. None of the flaws touch private keys or allow coin theft; the risk is disruption, draining the nodes that validate transactions and relay blocks across the network.

The Core Conflict: Speed of Disclosure Versus Speed of Attackers

The accelerated response was deliberate. Bitcoin Core’s security policy now calls for immediate disclosure once fixes become available for easily discoverable weaknesses, including those detectable through relatively simple AI-assisted scanning. The logic is blunt: if a language model can find the bug, so can anyone else’s language model. Sitting on patches while users run vulnerable software is no longer the conservative choice it once seemed.

But the patches do not erase every exposure. Bitcoin Core warned that 32-bit systems and nodes storing blockchain data on FAT32 file systems remain susceptible to the file-overflow issue in specific conditions. The 32.1 release notes also confirm that version 29.x and older branches have reached end of life, meaning operators on those releases get no future security updates even if they install the 29.5 patch. Moving to maintained versions requires macOS 14 or newer and Windows 10 version 1903 or newer for Bitcoin Core 32.1, and migrations from obsolete releases may need extra time for data-directory moves.

Market Implications for Everyday Investors

For holders, the reassuring part is what did not happen: no funds were at risk, and the network kept running. The unsettling part is the new baseline. The same AI wave that is reshaping every industry is now a permanent part of offense and defense in crypto security. Researchers have already used AI to find a flaw in the XRP Ledger that could theoretically mint trillions of tokens, and Bitcoin is getting the same treatment. Expect faster disclosure cycles, more advisories, and more pressure on anyone running stale software.

The Verdict

This episode is a net positive for Bitcoin’s long-term health: weaknesses were found by friendly scanners, fixed quickly, and disclosed honestly. The burden now shifts to operators, exchanges, and hobbyists running nodes to actually install the updates. If you rely on a third party to hold your bitcoin, the practical question is simple: ask whether their infrastructure runs maintained software. In an era where AI finds bugs in days, being three versions behind is not caution, it is risk.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

🌱 FOR BUSINESSES BitcoinsNews.com
Reach 100K+ Crypto Readers
Sponsored content, press releases, banner ads, and newsletter placements. Put your brand in front of Bitcoin's most engaged audience.

28 thoughts on “AI Found Three Bitcoin Core Security Flaws: Why Node Operators Must Update Now”

  1. updated my node within an hour of the advisory. the remote crash on windows is nastier than low severity sounds, a single hostile peer can trigger it

    1. which build are you on? running 29.x here and the notes were light on whether anything before 29.5 is affected at all

      1. 29.5 is the cutoff, anything older carries both memory exhaustion bugs. windows and macos nodes especially. patched mine before coffee

      2. Bjorn, everything before 29.5 is affected, the advisory lists fixes in 29.5, 30.4, 31.2 and 32.1. any older branch and you are running the memory exhaustion bugs

    2. upgraded both of mine within the hour too. the windows remote crash one is the scary one, a single hostile peer is trivial to arrange

  2. an AI found flaws humans missed for years in software securing a trillion dollars. the audit wars just went automated, expect a flood of these advisories

    1. fixes landed in 29.5, 30.4, 31.2 and 32.1. so anything older than 29.5 should be treated as affected, the advisory was light on that distinction

  3. updated two nodes to 30.4 yesterday, ten minutes each. the memory exhaustion one matters most, a hostile peer rebooting windows nodes is free griefing

  4. project loupe finding memory exhaustion bugs before humans did is a bigger story than the bugs themselves. llms auditing the software securing billions

    1. the rohrer team still validated every finding before disclosure though. llm flags candidates, humans confirm. that is a sane pipeline, not automated audits shipping straight to advisories

      1. the human confirmation step is the entire ballgame. the day a finding ships to an advisory unverified is the day this stops being good news for every chain, not just btc

    2. double edged though. if an llm can find these flaws cheaply, so can people with worse intentions. the disclosure race speeds up for everyone

      1. this is the part everyone keeps skipping. project loupe is public now, so every security team and every attacker knows llm fuzzing works on bitcoin core. disclosure race speeds up on both sides

        1. the llm that found these was apparently prompted by the maintainers themselves. imagine the same sweep run by someone who quietly reports to the wrong bug bounty

          1. ^ this is the uncomfortable part. the same sweep costs a few dollars to run and most node ops update slower than researchers disclose

          2. node ops updating slower than researchers disclose is the eternal constant. half the network still runs two branches back on principle

          3. maintainers prompting the sweep first is the only reason this reads as good news. the same loupe pipeline is public now for anyone with worse incentives

          4. the pipeline being public is the part that ages badly. maintainers got the friendly version, the next sweep might be one patch diff away from an exploit

          5. loupe being public cuts both ways but patch latency won this round. every affected branch got a fix the same day, attackers got zero head start

          6. maintainers got first crack this time because they ran the sweep themselves. next cycle the same scan runs quietly for weeks before any patch ships

          7. gap between an advisory and a working exploit on memory exhaustion bugs is not big. hoping core ships patches faster than the public scanners find them now

          8. private disclosure to maintainers first is the only reason this cycle worked. the same sweep by anon researchers becomes a zero day market overnight

          9. loupe being public means the disclosure countdown starts the second a model flags something. patch latency is now the only line of defense and everyone runs two branches back

  5. updated to 29.5 the minute i saw the advisory. if you’re on windows especially, a remote crash from a malicious peer is not theoretical

  6. humbling that a model found three bugs in the most audited codebase on earth. also the best possible ad for ai fuzzing

  7. three flaws, one remotely crashable on windows, found by a model. my 2013 self would not believe the audit pipeline is an llm prompt now

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$75,152.00+0.4%ETH$2,130.37+0.0%SOL$86.46-0.2%BNB$689.31+0.6%XRP$1.10-1.5%ADA$0.1768+0.8%DOGE$0.0699+1.2%DOT$0.8548-0.9%AVAX$8.62+8.6%LINK$10.63+2.1%UNI$6.97+2.6%ATOM$1.36+4.7%LTC$51.26+2.1%ARB$0.1742+4.9%NEAR$3.62+0.7%FIL$0.7600+2.3%SUI$0.8423+2.4%BTC$75,152.00+0.4%ETH$2,130.37+0.0%SOL$86.46-0.2%BNB$689.31+0.6%XRP$1.10-1.5%ADA$0.1768+0.8%DOGE$0.0699+1.2%DOT$0.8548-0.9%AVAX$8.62+8.6%LINK$10.63+2.1%UNI$6.97+2.6%ATOM$1.36+4.7%LTC$51.26+2.1%ARB$0.1742+4.9%NEAR$3.62+0.7%FIL$0.7600+2.3%SUI$0.8423+2.4%
Scroll to Top