Read the docs

Out-of-memory issue in Bitcoin Core

Priority LOW 30CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-400.

Summary

Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is affected. Uncontrolled resource consumption (CWE-400) can exhaust memory and cause an out-of-memory condition. A remote attacker without privileges or user interaction can degrade the availability of the affected node.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Description from the CNA

Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00304 23rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Bitcoin Core.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Timeline

  1. 2026-10-30 Threatist record created from CVE-2026-117349
  2. 2026-10-30 Alias added: GHSA-5q8q-px2m-hfmx
  3. 2026-11-02 CVSS score added · CISA ADP
  4. 2026-11-02 Weakness changed · CISA ADP
  5. 2026-11-02 CISA SSVC decision points changed

References

Sources