CVE-2020-25816
MEDIUM
6.8
CVSS Score
Published: September 30, 2020 at 07:44 PM UTC
Updated: June 17, 2026 at 03:07 AM UTC
1 product affected across 1 vendorVault
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.8
Exploit prediction
EPSS 1%
Description
HashiCorp Vault and Vault Enterprise versions 1.0 and newer allowed leases created with a batch token to outlive their TTL because expiration time was not scheduled correctly. Fixed in 1.4.7 and 1.5.4.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
1.0.0 ≤ v < 1.4.71.5.0 ≤ v < 1.5.4
Affected range stops below 1.4.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.5.4, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (2)
x_refsource_CONFIRMRelease NotesThird Party Advisory
Source: [email protected]
https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#154x_refsource_MISCVendor Advisory
Source: [email protected]
https://www.hashicorp.com/blog/category/vaultCVSS
- Attack Vector
- NETWORK
- Complexity
- HIGH
- Privileges
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- HIGH
- Availability
- NONE
Vector?
Quick Info
StatusMODIFIED
CWE
NVD-CWE-noinfo
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card