Markets
BTC $59,020 +1.98% ETH $1,660 +1.60% BNB $538 +2.47% XRP $0.9137 +1.78% SOL $69.10 +1.52% LINK $8.54 +2.02% BTC $59,020 +1.98% ETH $1,660 +1.60% BNB $538 +2.47% XRP $0.9137 +1.78% SOL $69.10 +1.52% LINK $8.54 +2.02% TOTAL $2.05T BTC.D 57.7%

Blockchain Technology

Bitcoin Core Patches a Node-Stalling Flaw Found by an AI Scanner

An AI-assisted audit found a bug that let a single message stall a Bitcoin node, and patches are now out for three release branches.

Bitcoin Core has shipped fixes for a medium-severity flaw that allowed a hostile peer to freeze a node for more than 12 seconds with a single crafted message. The project disclosed the bug on Nov. 20 and published patched releases for every maintained branch except the discontinued 29.x line.

The vulnerability is catalogued as CVE-2026-117348 and described as a node stall through duplicate orphan announcements. Versions 29.0 through 29.5, 30.0 through 30.4 and 31.0 through 31.2 are affected. Fixes are available in 30.5, 31.3 and 32.1.

The attack exploited Bitcoin Core’s orphanage, the holding area where transactions wait for missing parent transactions. When a peer announces one of those orphans, the node inspects its dependencies to work out what it needs to request. Inventory messages can carry up to 50,000 entries, and the software did not discard duplicate announcements. An attacker could point at the same orphan, with thousands of missing parents, over and over, forcing the node to repeat the same expensive checks thousands of times inside one message.

The result was a temporary denial of service: the targeted node stopped processing blocks and other traffic while it worked through the duplicates. The advisory describes no route to steal coins or damage a node permanently. The patch makes the software process each unique announcement once per inventory message.

The find came from Project Loupe, an automated security effort built on large language models by Elias Rohrer at Spiral, Block’s open-source Bitcoin development arm. The tool reported the issue on July 8. Bitcoin Core developer Gregory Sanders validated it and brought it to the security team. An independent researcher known as Stutxo filed a second report on Aug. 4, the same day Sanders opened the corrective pull request. The fix merged on Aug. 6 and reached Bitcoin Core 32.1 on Oct. 27, with the Nov. 20 disclosure accompanied by backports to older branches.

Node operators on affected versions have to upgrade to receive the fix, and the 29.x branch will not get one, which leaves any remaining users of that release exposed to a known denial-of-service vector.

The episode adds to a year of AI-assisted audits turning up weaknesses in crypto infrastructure. An earlier review in February caught a signature-verification flaw in the XRP Ledger’s proposed Batch amendment before it was activated, a reminder that automated code review is now part of the patch pipeline rather than a novelty.

Share this article

Viber uses viber://forward?text= when the app is installed.