infrastructure
Bitcoin Core patches 50,000-ID orphan-INV stall in 30.5 and 31.3
First CVE under Core's 'easy-to-find' policy: a repeated wtxid in an INV message stalls affected nodes for 12+ seconds. Fix shipped Nov 20 after an LLM scan.
Bitcoin Core maintainers published advisory CVE-2026-117348 on November 20, 2026, and released 30.5 and 31.3 the same day. The bug: a peer can repeat one transaction wtxid up to 50,000 times inside a single inv message and stall an affected node for more than a dozen seconds per message. The fix, PR #35878, had been in master since August.
This is the first CVE disclosed under the project's new "easy-to-find" security policy, adopted via PR #1281 on October 22. Under that policy, bugs that an attacker can rediscover from source with an LLM ship fixes to every supported release as quickly as the backports allow, with full details attached rather than embargoed.
The bug
From the advisory:
- When a peer announces a transaction by
wtxidand thatwtxidis already in the orphanage, the node lists the orphan's parents and checks each one against its mempool and recently-seen filters. - Duplicate entries in an
invmessage were not skipped. Aninvcan hold up to 50,000 entries. - An attacker crafts an orphan with thousands of missing parents, then repeats its
wtxid50,000 times in aninv. Each message makes the node redo the parent lookups N × 50,000 times. "Each such message stalls the node for over a dozen seconds," per the advisory. - During the stall, the node ignores messages from other peers — including new blocks. The attacker can chain more messages to extend the disruption.
Severity: Medium. Classification: Easily discoverable, which triggered the new policy's accelerated public-fix track.
Affected and fixed versions
| Series | Affected | Fixed |
|---|---|---|
| 29.x | 29.0 – 29.5 | Not fixed (series is end-of-life) |
| 30.x | 30.0 – 30.4 | 30.5 (2026-11-20) |
| 31.x | 31.0 – 31.2 | 31.3 (2026-11-20) |
| 32.x | — | 32.1 (already includes it; released 2026-10-27) |
Node operators running 29.x should migrate before the next disruption; the series will not get this fix.
Who found it
- Primary credit: Elias Rohrer's Project Loupe at Spiral, Block's open-source Bitcoin development unit. An automated LLM scan of Bitcoin Core's P2P code surfaced the bug.
- Validation and disclosure: Gregory Sanders validated the issue and reported it to the Bitcoin Core security team.
- Independent reporter:
stutxofiled the same bug on 2026-08-04, the day PR #35878 (the fix) was opened; the two reports arrived within hours of each other.
Timeline
- 2026-08-04:
stutxoreports; Loupe's scan independently flags the same path. PR #35878 opened. - 2026-08-06: PR #35878 merged to master.
- 2026-10-22: Bitcoin Core merges PR #1281 on bitcoincore.org, formalising the easy-to-find category.
- 2026-10-27: 32.1 released with the fix in-line (one of the three LLM-surfaced fixes in that batch).
- 2026-11-20: CVE-2026-117348 published; 30.5 and 31.3 ship the backports.
Impact and pattern
A stalled node is not a stolen coin, but the knock-on effects are real. The advisory notes that an attacker can keep a victim offline across a block arrival. For exchanges, that means delayed deposit crediting. For miners, it means operating on a stale chain tip — a window during which a privately-mined block becomes more attractive, with obvious implications for stale-share rates and, at the margin, selfish-mining viability.
The broader pattern: Loupe-at-Spiral is now the second confirmed LLM-assisted disclosure batch in Bitcoin Core in under a month, after the three fixes shipped in 32.1 on October 29. The new policy exists because scans that a lone researcher can run in an afternoon will keep producing medium-severity P2P bugs faster than embargo cycles can absorb. Today is the first disclosure to actually test the policy — and it did what it said it would, with details on-site the day the backports landed.
What to watch
- Mandatory 30.x upgrade on any production node still on 30.0 – 30.4. The patch is a one-line dedupe; the stall is not.
- 29.x migration deadline. Core has drawn a line: the 29.x series is EOL and will not get this fix. Operators on it are owning the risk.
- The next advisory under the "easy-find" track. PR #1281's whole point is that there will be more; the pipeline is now the news, not the one-off.
Sources: bitcoincore.org advisory, CoinDesk, Project Loupe, Bitcoin Core PR #35878.