How severe is CVE-2020-25816?

CVE-2020-25816 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2020-25816 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-25816?

CVE-2020-25816 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-25816?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-25816 published?

CVE-2020-25816 was published on 2020-09-30 and last updated on 2026-06-17.

CVE-2020-25816

CVE-2020-25816 is a medium-severity vulnerability in Hashicorp Vault with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
CVSS v2: 4.9
EPSS exploit prediction: 1% (59th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Hashicorp Vault
Published: 2020-09-30
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2020-25816?: 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.
How severe is CVE-2020-25816?: CVE-2020-25816 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-25816 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-25816?: CVE-2020-25816 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-25816?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-25816 published?: CVE-2020-25816 was published on 2020-09-30 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Hashicorp Vault

CVE-2020-35192 — Critical (CVSS 9.8): The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker…
CVE-2020-12757 — Critical (CVSS 9.8): HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly…
CVE-2025-6000 — Critical (CVSS 9.1): A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution…
CVE-2022-40186 — Critical (CVSS 9.1): An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine…
CVE-2022-36129 — Critical (CVSS 9.1): HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an…
CVE-2020-10661 — Critical (CVSS 9.1): HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing…

All CVEs affecting Hashicorp Vault →