bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dump…

published 2021-01-21 5y ago modified 2026-06-17 4mo ago also EUVD-2021-26536

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

bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dumpwallet RPC call. NOTE: this reportedly does not violate the security model of Bitcoin Core, but can violate the security model of a fork that has implemented dumpwallet restrictions

Patch / fix

distros 2

opensuse alpine

bitcoin openSUSE Leap 16.0 27.1-bp160.2.1
bitcoin Package Hub 15 SP3, openSUSE Leap 15.3 0.21.2-bp153.2.3.1

opensuse advisories openSUSE-SU-2026:21149-1 openSUSE-SU-2022:0072-1

bitcoin Alpine 3.18, Alpine 3.17, Alpine 3.16 +2 more 0.21.1-r0

alpine advisories ALPINE-CVE-2021-3195

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2021-3195 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.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/bitcoin/bitcoin/issues/20866 referenced PoC, tagged "exploit" by a source, unverified

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:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-20 Improper Input Validation

References

github.com /bitcoin/bitcoin/issues/20866
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2021-3195
NVD CVE-2021-3195

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.