Bitcoin Core 29.5, 30.4, 31.2 and 32.1 fix three AI-found bugs, including a remote crash of Windows, macOS and BSD nodes
Published Sources: pwn.watch
What is affected, what to do
Bitcoin Core published three advisories on Oct 28 2026 for bugs first found by an automated LLM scan (Elias Rohrer's Project Loupe at Spiral) and validated by Gregory Sanders. The worst, rated Medium: on platforms other than Linux, a malicious peer can send TCP urgent (out-of-band) data to bypass read backpressure and queue unlimited data, which Bitcoin Core says lets it "trivially crash any Windows, macOS or BSD node it is connected to".
The available sources name no fixed version. Check the vendor guidance in the references below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Bitcoin Core published three advisories on Oct 28 2026 for bugs first found by an automated LLM scan (Elias Rohrer's Project Loupe at Spiral) and validated by Gregory Sanders. The worst, rated Medium: on platforms other than Linux, a malicious peer can send TCP urgent (out-of-band) data to bypass read backpressure and queue unlimited data, which Bitcoin Core says lets it "trivially crash any Windows, macOS or BSD node it is connected to". A second Medium bug lets a peer that claims not to support BIP 31 pings stay paused forever while its message queue grows (up to 2MB per hour per inbound peer, 5MB per hour per outbound peer). A Low-severity undo-file overflow lets a miner corrupt other nodes' undo data, impractical on 64-bit systems. All three are fixed in 29.5, 30.4, 31.2 and 32.1 and were disclosed early under Core's new policy for "easily discoverable" bugs.
Source: pwn.watch