Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145)GHSA-hx3r-jv9q-85jw

HIGH

GHSA-hx3r-jv9q-85jw is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in bcoin. 1 public exploit reference exists, so weaponization risk is real. A fix is available for bcoin — see the affected versions and patch details below.

Also known asCVE-2018-17145
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
0.00%1.69%3.39%5.08%1.0%4.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-hx3r-jv9q-85jw by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

bcoinnpm
410downloads / week

Description

There was an easily exploitable uncontrolled memory resource consumption denial-of-service vulnerability that existed in the peer-to-peer network code of three implementations of Bitcoin and several alternative chains.

For more details please see: https://invdos.net/

For the paper: https://invdos.net/paper/CVE-2018-17145.pdf

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbcoinall versions1.0.2npm install bcoin@1.0.2

Affected Products

7 products · 24 configurations
Application
bcoinbcoin
< 1.0.2
range
Application
bitcoin corebitcoin
≥ 0.16.0 && < 0.16.2
range
Application
bitcoin knotsbitcoinknots
≥ 0.16.0 && < 0.16.2
range
Application
btcdbtcd_project
17 versions
0.3.00.3.10.3.20.3.30.4.00.5.00.6.00.7.00.8.00.9.00.10.00.11.0
Application
dcrddecred
< 1.5.2
range
Application
litecoinlitecoin
≥ 0.16.0 && < 0.16.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bcoin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update bcoin to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx3r-jv9q-85jw is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

There was an easily exploitable uncontrolled memory resource consumption denial-of-service vulnerability that existed in the peer-to-peer network code of three implementations of Bitcoin and several alternative chains. For more details please see: https://invdos.net/ For the paper: https://invdos.net/paper/CVE-2018-17145.pdf
O3 Security · Impact-Aware SCA

Is GHSA-hx3r-jv9q-85jw in your dependencies?

Find it across npm, including transitive dependencies.

Bitcoin Inventory Out-of-Memory Denial-of-Service Attack…