Bitcoin Core Fixes AI-Found Bug That Could Stall Nodes

35Importance
updatingStatus
2News media
Published
Updated

Bitcoin Core disclosed a medium-severity vulnerability on November 20, 2026, and released patched versions 30.5 and 31.3. The older 29.x branch will not receive a fix, while version 32.1 already included the patch.

Key claims & sources

✓
Versions 30.5 and 31.3 patch a medium-severity flaw found through Spiral’s Loupe scanner.
✓
The retired 29.x branch will not get a fix.
✓
Bitcoin Core disclosed CVE-2026-117348 on November 20, 2026, and released versions 30.5 and 31.3 to address a medium-severity flaw that could temporarily interrupt a node’s processing of blocks and transactions.
✓
Version 32.1 already contained the fix, and the affected releases ran from 29.0–29.5, 30.0–30.4, and 31.0–31.2.

What it means

Bitcoin Core is the software many nodes use to validate and relay Bitcoin blocks and transactions, so a patch landing in active releases is operationally important for node operators. This case sits in the standard release cycle: newer branches get updates, while an older retired branch does not. Version 32.1 already had the fix, which means some users were already on patched code before the November 20 disclosure.

A bug that can stall nodes goes to the core of Bitcoin’s networking layer, because nodes are the software’s gatekeepers for block and transaction processing. The fact that Spiral’s Loupe scanner found the flaw also points to a growing role for automated analysis in auditing widely used crypto infrastructure. The trade-off is straightforward: faster detection is useful, but the ecosystem still depends on operators keeping pace with branch-by-branch releases instead of assuming every line will be maintained forever.

Still unresolved is how many nodes were exposed before the patch and how widely the vulnerable versions were deployed. The disclosures identify the affected ranges and the branch that will not be fixed, but they do not say whether anyone observed the stall in live use. What would settle that is evidence from operators or incident data showing where the flaw appeared and whether upgrades were completed.

Market reaction i

BitcoinBTC it is the asset of the company or protocol in the event

Bitcoin rose 4.0% in the 4 hours after the first headline, after rising 0.1% in the 2 hours before.

$55,715 price at the headline
+0.1% 2 h before
+4.0% 4 h after
+7.8% 11 h after (so far)
First headline

45 prices, one every 30 minutes

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 21 06:29
The Defiant scoop
Breaks the event
+10 h 33 m
Nov 21 17:02
MEXC context
Its angle: vulnerability, transactions, temporarily