CoinDesk reported that Bitcoin Core disclosed CVE-2026-117348 on November 20, 2026, a medium-severity vulnerability in orphan transaction handling that allowed an attacker to stall a node's m
CoinDesk reported that Bitcoin Core disclosed CVE-2026-117348 on November 20, 2026, a medium-severity vulnerability in orphan transaction handling that allowed an attacker to stall a node's message processing for over 12 seconds per malicious inv message, blocking all peer communication including block propagation, according to CoinDesk's reporting on the disclosure. The flaw was already patched before public disclosure, with fixed releases distributed to operators on the same day the vulnerability was announced.
CoinDesk Reports a Fixed Node Message Processing Vulnerability
What Bitcoin Core confirmed
The vulnerability, introduced in Bitcoin Core v29.0, exploited a gap in how the software processed inv (inventory) messages used by nodes to announce transactions across the peer-to-peer network. A single inv message can carry up to 50,000 entries, and because duplicate transaction IDs were not filtered during orphan transaction handling, an attacker could flood a message with the same ID repeated up to 50,000 times, forcing the node to process redundant lookups and stall for more than 12 seconds per message, according to CoinDesk's reporting on the disclosure. For related coverage, see Bitcoin ETF Outflows: US Session Roundup.
The fix is a single logical change: process each transaction announced in an inv message only once. That change was merged via pull request #35878 on August 6, 2026, roughly one month after the flaw was first discovered, according to CoinDesk's reporting on the disclosure. Context on this theme: Hashi Mainnet is Live With 20-Plus Partners, Bringing Bitcoin Finance to Sui at Scale.
Affected versions span three release branches. Versions 29.0 through 29.5 carry the bug with no available patch, as that branch reached end-of-life status, according to CoinDesk's reporting on the disclosure. Versions 30.0 through 30.4 are fixed in 30.5, and versions 31.0 through 31.2 are fixed in 31.3, with both patched releases issued November 20, 2026. Bitcoin Core 32.1, released October 27, 2026, also incorporated the fix. More on this in Crypto Staking Dashboard Estimates Q4 2026: Rates and Risks Before Year-End.
What a Message-Processing Stall Means for Bitcoin Nodes
Why node operators should pay attention
Bitcoin nodes maintain network consensus by continuously exchanging messages with peers: they announce new transactions, request blocks, and relay confirmations. A stall of over 12 seconds per malicious message does not merely slow one operation; it blocks all peer communication for that node during the stall window, including block propagation. For a network where block intervals average 10 minutes, repeated stalls could cause a node to fall behind the chain tip.
Analysis: The practical consequences for node operators running infrastructure at exchanges or mining pools carry real commercial weight. According to CoinDesk reporting on the disclosure, exchanges could face delays in crediting deposits if their nodes miss block propagation during a stall, while miners could waste computational resources working on an outdated blockchain state rather than the current chain tip. Neither consequence requires a successful network-wide attack; a targeted campaign against specific infrastructure nodes would be sufficient.
Analysis: The severity rating of "medium" and the classification of "easily discoverable" are consequential distinctions. A medium rating indicates the attack does not threaten funds directly or allow chain rewriting, but the "easily discoverable" label carries its own urgency because it triggers an accelerated disclosure timeline under Bitcoin Core's updated policy, described in detail below. Bitcoin is trading at $58,268 as of the disclosure date, per CoinGecko data, with a market cap of approximately $1.172 trillion, amplifying the institutional stakes of infrastructure reliability at this scale.
An AI Scanner Found the Bug Before Any Known Attacker Did
The vulnerability was first identified on July 8, 2026 by Loupe, an automated LLM-powered vulnerability scanner built by Elias Rohrer at Spiral, the Bitcoin-focused development company backed by Block, Jack Dorsey's payments firm. Gregory Sanders, a Bitcoin Core contributor, validated and escalated the finding. A second independent researcher identified only as Stutxo filed a separate report on August 4, 2026, confirming the flaw was re-discoverable by individuals working without knowledge of the initial Loupe report, according to CoinDesk's reporting on the disclosure.
Spiral announced Loupe with the stated rationale: "Meet Loupe, an AI-powered vulnerability scanner for open-source bitcoin projects. Attackers already use AI to find weaknesses. Maintainers should do the same," according to a post from @spiral_xyz on X. Analysis: The dual-report scenario, in which an AI scanner and a human researcher independently converged on the same flaw within four weeks, illustrates the threat model Loupe was designed to address.
"Meet Loupe, an AI-powered vulnerability scanner for open-source bitcoin projects. Attackers already use AI to find weaknesses. Maintainers should do the same."
Spiral (@spiral_xyz), via X
A New Disclosure Policy Accelerated the Public Timeline
Keeping critical infrastructure maintained
Bitcoin Core adopted an updated vulnerability disclosure policy on October 22, 2026, that mandates rapid public disclosure for bugs classified as "easily discoverable," according to CoinDesk's reporting on the advisory. Analysis: The policy change may reflect a structural shift in the threat environment: when AI tools can scan open-source codebases and surface exploitable logic errors in days rather than months, the traditional responsible disclosure window, which typically runs 90 days or longer, may create an asymmetric risk. Defenders working through the standard timeline may still be distributing patches while adversaries with equivalent tooling have already independently identified the same flaw.
Analysis: The significance for the broader Bitcoin infrastructure ecosystem may extend beyond a single CVE. As Bitcoin's market cap hovers near $1.172 trillion and institutional Bitcoin ETF holdings reached record levels after Q3, the attack surface of critical node software draws more attention from adversarial actors, making proactive AI-assisted scanning a credible operational necessity rather than a research experiment.
What Node Operators Should Check After the Fix
Operators running Bitcoin Core versions 30.0 through 30.4 should upgrade to 30.5; those on 31.0 through 31.2 should upgrade to 31.3. Both releases were made available on November 20, 2026, the same date as this disclosure, according to CoinDesk's reporting on the disclosure. Operators already running 32.1 or later are not affected. Those still on the 29.x branch should consult Bitcoin Core's official release notes and security communications directly, as that branch has reached end-of-life and no patch has been issued for it.
The recommended upgrade path is to follow Bitcoin Core's documented release and verification procedures appropriate to each operator's environment. The fix itself is minimal in scope, targeting only the deduplication logic within inv message processing, which limits the risk of unintended side effects from the upgrade. Operators running nodes as part of exchange infrastructure or mining operations should treat the upgrade as time-sensitive given the confirmed ability of the unpatched vulnerability to disrupt block propagation.
FAQ: Bitcoin Core's Fixed Message-Processing Vulnerability
Was the vulnerability fixed before public disclosure?
CoinDesk reported that the fix was merged on August 6, 2026, and distributed in Bitcoin Core 32.1 on October 27, 2026, nearly four weeks before the November 20 public disclosure date. Patched releases for the 30.x and 31.x branches were released simultaneously with the public announcement.
Could it halt node message processing?
According to CoinDesk's reporting on the disclosure, a single malicious inv message could cause a node to stall for over 12 seconds, blocking all peer communication during that window. An attacker sending messages continuously could keep a targeted node effectively disconnected from the network for extended periods.
Which versions were affected?
CoinDesk reported that versions 29.0 through 29.5 had no patch available because the branch was end-of-life, while versions 30.0 through 30.4 were patched in 30.5 and versions 31.0 through 31.2 were patched in 31.3. Operators should verify their specific version against Bitcoin Core's release communications before assuming their installation falls outside the affected range.
What should node operators do?
Operators on 30.x or 31.x should upgrade to the patched releases issued November 20, 2026. Operators on 29.x should consult Bitcoin Core's official channels for guidance, as no patch has been issued for that branch. Operators on 32.1 or later are already running fixed software. All operators should verify their version and consult Bitcoin Core's official channels for upgrade instructions.
How was the vulnerability discovered?
Loupe, an AI-powered open-source vulnerability scanner developed by Elias Rohrer at Spiral, identified the flaw on July 8, 2026. Bitcoin Core contributor Gregory Sanders validated and escalated the finding. Researcher Stutxo independently reported the same vulnerability on August 4, 2026, confirming it was re-discoverable by a second party without knowledge of the original report, according to CoinDesk's reporting on the disclosure. The dual-discovery event directly informed the accelerated disclosure timeline applied under Bitcoin Core's updated policy adopted October 22, 2026.
Analysis: With Bitcoin's Fear and Greed Index sitting at 12 (Extreme Fear) as of the disclosure date per Alternative.me data, and the asset trading roughly 54% below its all-time high of $126,080, the November 20 disclosure arrives during a period of compressed market confidence. The vulnerability's already-fixed status limits immediate security risk, but operators who have not yet upgraded to patched releases face an exploitable window that grows narrower only after they act. The next concrete milestone to watch is whether Bitcoin Core's accelerated AI-discovery disclosure policy, formalized October 22, draws formal adoption by other major open-source Bitcoin infrastructure projects facing the same asymmetric threat environment.
Editorial credits
EZ
Elena Zenth
Writer · Coincu
HN
Haruto Nakamura
Editor · Coincu
Monitors published articles around the clock and can correct or withdraw them.
Checked by Coincu QC Team before publishing on November 21, 2026 for headline accuracy, factual consistency, metadata, commercial disclosure and authorship claims: our AI review system checks every article before it goes live, and our editor monitors it after publication. Report an error.
Coincu uses AI for research, drafting and review. Our editorial team is responsible for every article and corrects or withdraws articles when needed. How we review.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
The post Report: Bitcoin Core Fixes Node Message Processing Vulnerability was initially published on Coincu.