CVE-2020-16250: Authentication Bypass in Hashicorp Vault
Summary
CVE-2020-16250: Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault. Affects github.com/hashicorp/vault across 4 version ranges.
>= 0.8.1, < 1.2.5
>= 1.3.0, < 1.3.8
>= 1.4.0, < 1.4.4
>= 1.5.0, < 1.5.1
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- vault · Bitnami
The same CVE-2020-16250 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
HashiCorp Vault is a popular open-source tool used for securely storing and accessing sensitive data. It provides a centralized solution for managing secrets, encryption keys, and other credentials. The vulnerability identified as CVE-2020-16250 affects versions 0.7.1 and newer of HashiCorp Vault, specifically when configured with the AWS IAM auth method. This vulnerability allows for authentication bypass, potentially leading to unauthorized access to sensitive information stored in the Vault.
Vulnerability Detail
The vulnerability arises from a combination of spoofing and insufficient verification of data authenticity in HashiCorp Vault. By exploiting this flaw, an attacker can bypass the authentication mechanism and gain unauthorized access to the Vault. This can lead to the exposure of sensitive data, compromise of encryption keys, and unauthorized modification of stored secrets. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.
How To Fix
Latest published version: v1.21.4 as of 23 Oct 2026
go get github.com/hashicorp/vault@v1.21.4Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 0.8.1, < 1.2.51.2.5go get github.com/hashicorp/vault@v1.2.5 -
>= 1.3.0, < 1.3.81.3.8go get github.com/hashicorp/vault@v1.3.8 -
>= 1.4.0, < 1.4.41.4.4go get github.com/hashicorp/vault@v1.4.4 -
>= 1.5.0, < 1.5.11.5.1go get github.com/hashicorp/vault@v1.5.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the patched versions of HashiCorp Vault.
Conclusion
The authentication bypass vulnerability in HashiCorp Vault poses a significant risk to the security of sensitive data stored in the Vault. It is crucial to upgrade to the latest patched versions (1.2.5, 1.3.8, 1.4.4, or 1.5.1) to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/hashicorp/vault →
FAQ
HashiCorp Vault is an open-source tool used for securely storing and accessing sensitive data, such as secrets, encryption keys, and credentials.
The vulnerability allows for authentication bypass, potentially leading to unauthorized access to sensitive information stored in HashiCorp Vault. This can result in the exposure of sensitive data, compromise of encryption keys, and unauthorized modification of stored secrets.
Versions 0.7.1 and newer of HashiCorp Vault are affected by this vulnerability.
To fix this vulnerability, it is recommended to upgrade to the latest patched versions of HashiCorp Vault (1.2.5, 1.3.8, 1.4.4, or 1.5.1).
There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading to the patched versions of HashiCorp Vault.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/hashicorp/vault.
