Key Points:
- An AI-powered scanner identified a Bitcoin Core vulnerability that could temporarily prevent nodes from processing network messages by repeating a transaction ID up to 50,000 times.
- The flaw, tracked as CVE-2026-117348, could stall affected nodes for more than a dozen seconds per malicious message, potentially disrupting transaction processing and blockchain updates.
- Bitcoin Core released patched versions 30.5 and 31.3, addressing the issue by ensuring that repeated transaction announcements are processed only once.
An artificial intelligence-powered security scanner developed through Block’s Spiral initiative identified a vulnerability in Bitcoin Core that could temporarily disrupt a node’s ability to process messages from the Bitcoin network. The flaw, disclosed Friday and classified as medium severity, highlights how automated security tools are increasingly being used to identify weaknesses in critical blockchain infrastructure, while also reinforcing the importance of maintaining updated node software.
Repeated Transaction IDs Could Temporarily Stall Bitcoin Nodes
The vulnerability, identified as CVE-2026-117348, involved Bitcoin Core’s handling of transaction announcements containing repeated identifiers. According to the disclosed technical details, an attacker could exploit the software by sending an orphan transaction, a payment whose parent transaction has not yet been received by the node, followed by an announcement repeating that transaction ID up to 50,000 times.
Bitcoin nodes maintain records of orphan transactions and attempt to locate missing parent transactions when necessary. Since version 29.0, Bitcoin Core has generated lists of missing transaction dependencies and checked its records before deciding which information to request from other nodes. However, the software did not effectively skip repeated entries within a single announcement batch.
As a result, the node could repeatedly perform computationally expensive checks for the same transaction identifier. The security advisory stated that each malicious message could stall a node for more than a dozen seconds, during which it would be unable to process messages from other network participants, including newly announced blocks.
Potential Consequences for Exchanges and Mining Operations
Although the vulnerability did not represent a direct mechanism for stealing Bitcoin or altering the blockchain’s consensus rules, temporary node disruption could create operational consequences for businesses and infrastructure providers relying on affected software.
For example, a cryptocurrency exchange operating an affected node could experience delays in processing or crediting Bitcoin deposits. Mining operations could also face disruption if a node temporarily stops receiving or processing network updates, potentially leaving miners working with an outdated view of blockchain activity.
Repeated malicious messages could prolong the disruption, according to the advisory. This makes the vulnerability relevant to network availability and operational reliability rather than the direct compromise of user funds or private keys.
AI-Assisted Security Research Identifies the Flaw
The vulnerability was flagged by Project Loupe, an open-source scanning initiative associated with Spiral, Block’s open-source development unit. The automated system uses AI agents to examine Bitcoin code and identify potential security weaknesses. The advisory credited an automated scan conducted through the project led by Elias Rohrer.
Bitcoin Core developers classified the issue as medium severity and easily discoverable. Under the security policy adopted on October 22, 2026, easily discoverable vulnerabilities are addressed across maintained software versions as quickly as possible, accompanied by public advisories and releases.
Software Updates Address the Vulnerability
Bitcoin Core released versions 30.5 and 31.3 to address the issue. The patch ensures that each transaction announced within a batch is processed only once, preventing repeated identifiers from triggering redundant checks and potentially stalling message processing.
The incident underscores the growing role of AI in both cybersecurity research and the identification of software vulnerabilities. As automated tools make weaknesses easier to detect, Bitcoin infrastructure operators will increasingly need to prioritize timely updates, monitoring and operational resilience. The broader significance lies not in a compromise of Bitcoin’s underlying consensus system, but in the continuing effort to protect the network’s distributed infrastructure against disruptions that could affect the reliability of transaction processing.
Comparison, examination, and analysis between investment houses
Leave your details, and an expert from our team will get back to you as soon as possible