VulnerabilityPublished 30 Oct 2026

CVE-2026-117349: Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue

Source CVE Database V5

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:33 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Upgrading to Bitcoin Core versions 29.5, 30.4, 31.2, or 32.1 or later resolves this vulnerability. Users should apply these updates to mitigate the risk.

Description

Bitcoin Core versions prior to 29.5, 30.4, 31.2, and 32.1 contain a vulnerability that can cause an out-of-memory (OOM) condition.

Impact

An out-of-memory condition can cause the affected Bitcoin Core nodes to crash or become unresponsive, potentially disrupting normal operations. However, there is no indication of active exploitation or additional impact details.

Summary

The vulnerability identified as CVE-2026-117349 affects Bitcoin Core software versions before 29.5, 30.4, 31.2, and 32.1. It involves an out-of-memory (OOM) issue, which may lead to resource exhaustion. No further technical details or exploitation methods are provided in the available data.

References

Community reviews

Loading reviews…