CVE-2021-32923
Invalid session token expiration
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
7.4
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
CVE-2021-32923- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - CVSS 2.0
- 5.8 Medium
AV:N/AC:M/Au:N/C:P/I:P/A:N - Weakness
- CWE-613
- Updated
- 2026-11-02
CVE List No score
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
CVE-2021-32923- Updated
- 2026-11-02
EUVDEUVD-2021-1251 No score
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
EUVD-2021-1251- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-38j9-7pp9-2hjw
7.4
Invalid session token expiration
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
GHSA-38j9-7pp9-2hjw- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-613
- Updated
- 2026-11-02
OSVALPINE-CVE-2021-32923
7.4
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
ALPINE-CVE-2021-32923- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-03
OSV
7.4
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
CVE-2021-32923- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVGHSA-38j9-7pp9-2hjw
7.4
Invalid session token expiration
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
GHSA-38j9-7pp9-2hjw- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - Weakness
- CWE-613
- Updated
- 2026-11-02
OSVBIT-vault-2021-32923 No score
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 treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
- Record
BIT-vault-2021-32923- Updated
- 2026-11-02
OSVGO-2022-0623 No score
Invalid session token expiration in github.com/hashicorp/vault
Invalid session token expiration in github.com/hashicorp/vault
- Record
GO-2022-0623- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/hashicorp/vaultGo |
1.7.0 up to 1.7.2 | 1.7.2 |
github.com/hashicorp/vaultGo |
1.6.0 up to 1.6.5 | 1.6.5 |
github.com/hashicorp/vaultGo |
0.10.0 up to 1.5.9 | 1.5.9 |
vaultAlpine:v3.13 |
0.10.0 up to 1.5.9-r0 | 1.5.9-r0 |
vaultAlpine:v3.14 |
0.10.0 up to 1.7.2-r0 | 1.7.2-r0 |
vaultAlpine:v3.15 |
0.10.0 up to 1.7.2-r0 | 1.7.2-r0 |
vaultAlpine:v3.16 |
0.10.0 up to 1.7.2-r0 | 1.7.2-r0 |
vaultAlpine:v3.17 |
0.10.0 up to 1.7.2-r0 | 1.7.2-r0 |
vaultAlpine:v3.18 |
0.10.0 up to 1.7.2-r0 | 1.7.2-r0 |
vaultBitnami |
0.10.0 up to 1.5.9, 1.6.0 up to 1.6.5, 1.7.0 up to 1.7.2 | 1.5.91.6.51.7.2 |
github.com/hashicorp/vaultGo |
0.10.0 up to 1.5.9, 1.6.0 up to 1.6.5, 1.7.0 up to 1.7.2 | 1.5.91.6.51.7.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2021-32923 is a high vulnerability (CVSS 7.4) in Hashicorp Vault, published June 3, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.38%, the 72nd percentile. Fixed in github.com/hashicorp/vault 1.7.2.
References
hashicorp.com/blog/category/vault
discuss.hashicorp.com/t/hcsec-2021-15-vault-renewed-nearly-expired-leases-with-incorrect-non-expiring-ttls/24603
security.gentoo.org/glsa/202207-01
nvd.nist.gov/vuln/detail/CVE-2021-32923
github.com/advisories/GHSA-38j9-7pp9-2hjw
security.alpinelinux.org/vuln/CVE-2021-32923