Quick answers
- Is CVE-2026-117349 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117349 being exploited in the wild.
- How severe is CVE-2026-117349?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Bitcoin Bitcoin Core.
- Is there a fix for CVE-2026-117349?
- Yes: fixed in Bitcoin Core 29.5, 30.4, 31.2, 32.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117349 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-117349?
- Check whether you run Bitcoin Core. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Bitcoin Core 29.5, 30.4, 31.2, 32.1
Technical details
The vulnerability is an out-of-memory (OOM) condition caused by slow unbounded memory growth on paused pre-BIP31 peers. When peer send functionality is paused for legacy protocol peers, memory is not properly bounded, allowing memory exhaustion through connection handling. An unauthenticated network attacker can trigger this via specially crafted peer connections.
Affected products
- Bitcoin Bitcoin Core
Timeline
- 2026-10-28: disclosed
- 2026-10-30: advisory: NVD publication