The official vault docker images before 0.11.6 contain a blank password for a root user.

published 2020-12-17 5y ago modified 2026-09-08 2mo ago also BIT-vault-2020-35192 , EUVD-2020-22879

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

The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.

Patch / fix

fixed in 2

bitnami vault 0.11.6
hashicorp vault 0.11.6

Is CVE-2020-35192 in your dependencies? 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

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
bitnami	vault	>=0.6.0, <0.11.6	0.11.6

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality

References

github.com /koharin/koharin2/blob/main/CVE-2020-35192
third-party-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2020-35192
web

Sources

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.