VYPR
High severityNVD Advisory· Published Jun 3, 2021· Updated Aug 3, 2024

CVE-2021-32923

CVE-2021-32923

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

HashiCorp Vault had a flaw where renewing nearly-expired leases (within 1s of max TTL) caused them to be treated as non-expiring, allowing indefinite use. Fixed in 1.5.9, 1.6.5, 1.7.2.

Vulnerability

HashiCorp Vault and Vault Enterprise from version 0.10.0 through 1.7.1 contained a logic flaw in lease renewal. When a token lease or dynamic secret lease was renewed within the last second of its maximum TTL, the renewed lease was assigned a TTL of zero seconds (rounded down). This zero-second TTL was incorrectly interpreted as non-expiring by Vault’s internal accounting, allowing the lease to be used indefinitely [1][2].

Exploitation

To exploit this issue, an attacker must possess an existing valid Vault token. The vulnerability is triggered when a lease is renewed inside a narrow time window (the final second of its maximum TTL). Automation-driven renewals operating with tight time tolerances are more likely to hit this window. No additional authentication or network position beyond that required for normal lease renewal is needed [2].

Impact

Successfully exploited leases – both token leases and dynamic secret leases – are never revoked. This means tokens or dynamic secrets that should have expired remain valid indefinitely, potentially granting continued access to resources that were intended to be time-limited. The impact is a violation of the intended time-to-live policy, leading to unauthorized access or privilege persistence [2].

Mitigation

The vulnerability is fixed in Vault and Vault Enterprise versions 1.5.9, 1.6.5, and 1.7.2. Operators should upgrade to one of these releases or later. No workaround is known [2][3].

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
github.com/hashicorp/vaultGo
>= 1.7.0, < 1.7.21.7.2
github.com/hashicorp/vaultGo
>= 1.6.0, < 1.6.51.6.5
github.com/hashicorp/vaultGo
>= 0.10.0, < 1.5.91.5.9

Affected products

8

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

6

News mentions

0

No linked articles in our index yet.