VulnerabilityPublished 30 Oct 2026

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

Source GCVE Database

Compare

Authoritative record:CVE-2026-117350· Medium

Not known to be exploited · fixed in 32.1 : update service conditions. Bitcoin Core when convenient.

Data as of 30 Oct 2026, 17:02 UTC

Severity

Medium

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

Thin evidence

One scorer or none

Affects: service conditions. Bitcoin Core prior to 29.5
Patch: Available – fixed in 32.1, 31.2, 30.4 +1

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.

ghsa-hmp5-qx3x-m58f

What to do

AI-suggested

Users should upgrade to Bitcoin Core versions 29.5, 30.4, 31.2, or 32.1 or later, where this OOM issue is addressed. Since fixed versions are explicitly stated, applying these updates will remediate the vulnerability.

Description

Bitcoin Core versions prior to 29.5, 30.4, 31.2, and 32.1 are affected by an out-of-memory (OOM) issue. This vulnerability could cause the software to consume excessive memory, potentially leading to crashes or denial of service conditions.

Impact

The vulnerability can lead to out-of-memory conditions, which may cause Bitcoin Core nodes to crash or become unresponsive, potentially disrupting node availability and network participation. There is no indication of remote code execution or data compromise.

Summary

An out-of-memory (OOM) vulnerability exists in Bitcoin Core versions before 29.5, 30.4, 31.2, and 32.1. The flaw may cause the application to exhaust available memory resources, impacting stability and availability. No further technical details or exploitation methods are provided in the source data.

References

Community reviews

Loading reviews…