CVE-2020-25816

MEDIUMNVD 6.86.8

6.8

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.

CVSS v3: 6.8
EG Score: 6.8(low)
EPSS: 54.2%
KEV: Not listed

Published

September 30, 2020

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://github.com/hashicorp/vault/blob/master/CHANGELOG.md#154
cve@mitrehttps://www.hashicorp.com/blog/category/vault
af854a3a-2127-422b-91ae-364da2661108https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#154
af854a3a-2127-422b-91ae-364da2661108https://www.hashicorp.com/blog/category/vault

Affected Packages

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
github.com/hashicorp/vault	—	1.5.4	—

Data Freshness Timeline

(refreshed 11× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:48 UTCepss_batch
2026-05-23 07:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2020-25816?

CVE-2020-25816 is a medium vulnerability published on September 30, 2020. 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.

When was CVE-2020-25816 disclosed?

CVE-2020-25816 was first published in the National Vulnerability Database on September 30, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-25816 actively exploited?

CVE-2020-25816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-25816?

CVE-2020-25816 has a CVSS v3 base score of 6.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..

How do I remediate CVE-2020-25816?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-25816, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-25816

Explore →

Is Your Infrastructure Affected by CVE-2020-25816?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-25816

📅 Published

🔄 Last Modified

🔗 References (4)