Bitcoin Core disclosed a peer-to-peer networking flaw on November 20, 2026 that could temporarily stall an affected node’s processing of new blocks and transactions. The medium-severity vulnerability, CVE-2026-117348, arose when a malicious peer repeatedly advertised an orphan transaction. Bitcoin Core 30.5 and 31.3 shipped fixes alongside the public advisory; version 32.1 already included the correction after its October 27 release.
A Bitcoin full node independently verifies blocks and relays transactions to peers. Its mempool holds validated, unconfirmed transactions. An orphan transaction instead refers to one or more parent transactions the node has not yet received, so Bitcoin Core temporarily tracks it while seeking the missing parents. Developers designed the mechanism to help legitimate transfers propagate efficiently.
Gloria Zhao, Adopting Bitcoin, November 2021: original developer presentation on Bitcoin transaction-relay policy. Historical technical context, not footage of the newly disclosed vulnerability.
Why 50,000 repeated entries mattered
The Bitcoin Core advisory explains that a network inventory message, called inv, can contain up to 50,000 entries. Before the fix, affected software did not ignore duplicates when examining announcements of an orphan already in its tracking pool. Each repeated transaction identifier could trigger another search for missing parents and checks against the mempool and previously seen identifiers.
With a specially constructed orphan carrying many unknown parents, a single announcement batch could occupy processing for more than a dozen seconds. The affected node could not process incoming messages from other peers, including block announcements, during the stall. Repeating the traffic could prolong local disruption. The disclosure does not establish a network-wide outage or theft of bitcoin.
An AI-assisted scan raised the first alarm
The official timeline credits Elias Rohrer’s Project Loupe, an automated large-language-model code scan at Spiral, with reporting the weakness on July 8. A researcher identified as Stutxo independently reported it August 4. Gregory Sanders validated and presented the initial finding to the Bitcoin Core security team, then opened a fix on August 4; the change merged August 6.
The code change is deliberately narrow: process each unique transaction announcement only once per inventory message. Developers later backported it to maintained 30.x and 31.x branches. The November 20 public disclosure followed those releases, rather than announcing a new mainnet rule or soft fork.
Bitcoin Magazine’s Bitcoin 2022 mempool developer panel, linked by development nonprofit Brink. An archival discussion of relay policy and denial-of-service safeguards, not a live demonstration of CVE-2026-117348.
Which Bitcoin Core installations need an update?
The official affected ranges are 29.0–29.5, 30.0–30.4 and 31.0–31.2. Operators on the supported 30.x line can update to 30.5; operators on 31.x can update to 31.3. Version 32.1 also contains the fix. Bitcoin Core says the 29.x line is end-of-life and will not receive a branch-specific patch, so users should migrate to a maintained release.
The release notes advise stopping an older node cleanly before installing the replacement. Operators should confirm a downloaded build against the project’s authenticated release materials, back up wallet data, and read the compatibility notes before making changes. Running a node involves more than opening port 8333; software maintenance and reliable peer connectivity matter too. BitcoinVersus.Tech recently covered home-node connectivity behind NAT.
Why a temporary stall still matters
A delayed block could leave an exchange, wallet backend or mining operation using an outdated local view of the chain. However, temporarily halting a node’s message handling is not equivalent to rewriting a valid block, changing Bitcoin’s supply or defeating its consensus checks. A stalled installation may recover, but its availability remains a practical operational concern.
The bug follows other recently disclosed Bitcoin Core attack surfaces, while the site’s coverage of version 32.1 provides earlier release context. Developers also continue debating stale-block relay efficiency, a separate proposal, not a repair for the orphan bug. The central engineering lesson is straightforward: a small duplicate-processing check can protect a node from an outsized burst of wasted work.
Primary sources and related media
- Bitcoin Core, official CVE-2026-117348 advisory and July–November 2026 timeline
- Bitcoin Core 30.5 release notes, November 20, 2026; 31.3 announcement
- Bitcoin Core PR #35878, unique transaction inventory processing
- Brink developer media archive, confirming both historical speaker sessions
- Gloria Zhao, Adopting Bitcoin 2021; Bitcoin Magazine mempool panel, 2022
Editorial verification: Published version ranges, fix dates, technical mechanism and reporter attribution follow the Bitcoin Core advisory. The cover is original editorial colored-pencil illustration, not a photograph of a real compromised node. The embedded developer sessions explain older relay-policy concepts and do not document an attack in November 2026.
Editor’s Note: We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiatives, please scan the QR code below

For mobile scanning, open the article on another display and scan the QR code with a Bitcoin wallet. The voluntary donation amount is 5,000 sats. Verify the receiving address 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb before sending.
BitcoinVersus.Tech publishes technology and financial journalism for informational purposes and does not provide financial, investment, or legal advice.

Leave a Reply