Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when deserializing transactions.

published 2020-12-23 5y ago modified 2026-06-17 4mo ago also EUVD-2018-2068

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

Patch / fix

fixed in 1

bitcoinsv bitcoin_sv 0.1.1

Is CVE-2018-1000893 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption

References

bitcoinsv.io /2019/03/01/denial-of-service-vulnerabilities-repaired-in-bitcoin-sv-version-0-1-1/
vendor-advisory

Sources

CVE List CVE-2018-1000893
NVD CVE-2018-1000893

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.