CVE-2021-32923: Invalid session token expiration in HashiCorp Vault
Summary
CVE-2021-32923: Invalid session token expiration. Affects github.com/hashicorp/vault across 3 version ranges.
>= 0.10.0, < 1.5.9
>= 1.6.0, < 1.6.5
>= 1.7.0, < 1.7.2
Fixed in 1.5.9, 1.6.5 or 1.7.2, depending on the release line you run. How to fix ↓
Also tracked for
- vault · Bitnami
The same CVE-2021-32923 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 an open-source tool for securely accessing secrets and sensitive data in distributed systems. It provides a centralized platform for managing secrets, encryption keys, and other sensitive information. Vault is written in Go and is widely used in various applications and environments.
Vulnerability Detail
The vulnerability identified as CVE-2021-32923 in HashiCorp Vault and Vault Enterprise allows the renewal of nearly-expired token leases and dynamic secret leases. Tokens and secrets that were within 1 second of their maximum TTL (Time To Live) were incorrectly treated as non-expiring during subsequent use. This flaw could lead to the unauthorized access of sensitive information and compromise the security of the system. The vulnerability has a CVSS score of 7.4, indicating a high severity level.
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.10.0, < 1.5.91.5.9go get github.com/hashicorp/vault@v1.5.9 -
>= 1.6.0, < 1.6.51.6.5go get github.com/hashicorp/vault@v1.6.5 -
>= 1.7.0, < 1.7.21.7.2go get github.com/hashicorp/vault@v1.7.2
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 fixes by upgrading to the patched versions of HashiCorp Vault.
Conclusion
The vulnerability identified as CVE-2021-32923 in HashiCorp Vault allows the renewal of nearly-expired token leases and dynamic secret leases, incorrectly treating them as non-expiring. Upgrading to the patched versions of HashiCorp Vault (1.7.2, 1.6.5, or 1.5.9) is necessary to fix this vulnerability and ensure the security of the system. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/hashicorp/vault →
FAQ
HashiCorp Vault is an open-source tool for securely accessing secrets and sensitive data in distributed systems. It provides a centralized platform for managing secrets, encryption keys, and other sensitive information.
This vulnerability allows the renewal of nearly-expired token leases and dynamic secret leases, incorrectly treating them as non-expiring. It could lead to unauthorized access to sensitive information and compromise the security of the system.
The CVSS score of this vulnerability is 7.4, indicating a high severity level.
To fix this vulnerability, upgrade to the patched versions of HashiCorp Vault: 1.7.2, 1.6.5, or 1.5.9, depending on the version you are currently using.
There is no known workaround for this vulnerability. It is crucial to apply the recommended fixes by upgrading to the patched versions of HashiCorp Vault.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/hashicorp/vault.
