Vault vulnerabilitiesRanked by how likely they are to be used.
Vault is made by Hashicorp. We track 64 published vulnerabilities listed under that exact name, across 248 versions. None of them is on the list of flaws known to be exploited today. Hashicorp lists newer releases under their own names, such as Vault Provider for Secrets Store Csi Driver, so check those pages too.
We keep watching the known-exploited list.
Is Vault listed under other names? Yes.
Hashicorp also lists Vault under more specific names, such as Vault Provider for Secrets Store Csi Driver. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Vault vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Vault's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Vault flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.9%CVE-2020-35192Critical
The official vault docker images before 0.11.6 contain a blank password for a root user.
- 2.8%CVE-2020-16251High
HashiCorp Vault and Vault Enterprise versions 0.8.3 and newer, when configured with the GCP GCE auth method, may be vulnerable to authentication bypass.
- 1.6%CVE-2022-36129Critical
HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that could be abused to override the voter status of a node within a Vault...
- 1.5%CVE-2020-12757Critical
HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials with the default time-to-live lease duration instead of the...
- 1.5%CVE-2020-16250High
HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass.
- 1.5%CVE-2021-45042Medium
In HashiCorp Vault and Vault Enterprise before 1.7.7, 1.8.x before 1.8.6, and 1.9.x before 1.9.1, clusters using the Integrated Storage backend allowed an authenticated user (with write permissions to a kv secrets...
- 1.4%CVE-2020-7220High
HashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails, in certain circumstances, to revoke dynamic secrets for a mount in a deleted namespace.
- 1.4%CVE-2021-32923High
HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly...
- 1.4%CVE-2021-3024Medium
HashiCorp Vault and Vault Enterprise disclosed the internal IP address of the Vault node when responding to some invalid, unauthenticated HTTP requests.
- 1.4%CVE-2020-25594Medium
HashiCorp Vault and Vault Enterprise allowed for enumeration of Secrets Engine mount paths via unauthenticated HTTP requests.
Running Vault? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Vault on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 64 published vulnerabilities listed under the name Vault, across 248 versions.
None of Vault's vulnerabilities is on the list of flaws known to be exploited today.
Hashicorp also lists Vault under more specific names, such as Vault Provider for Secrets Store Csi Driver. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Vault. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.