Hashicorp Vault 1.21
Hashicorp Vault 1.21
The Hashicorp Vault 1.21 reached end of service life on Apr 13, 2026 — Hashicorp Vault no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Hashicorp Vault 1.21 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- hashicorp-vault
- release
- 1.21
- product Label
- Hashicorp Vault
- release Label
- 1.21
- codename
- lts
- latest Version
- 1.21.4
- release Date
- 2025-10-21
- maintained
- source Url
- https://endoflife.date/hashicorp-vault
Lifecycle Dates
- End of Service Life
- Apr 13, 2026
- Last OEM Support
- Apr 13, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Hashicorp Vault 1.21 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Hashicorp Vault 1.21?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Hashicorp Vault 1.21 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Hashicorp Vault 1.21 Support: Frequently Asked Questions
Is the Hashicorp Vault 1.21 still supported?
Hashicorp Vault ended support for the Hashicorp Vault 1.21 on Apr 13, 2026 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Hashicorp Vault 1.21 end of service life (EOSL) date?
Hashicorp Vault lists the end of service life for the Hashicorp Vault 1.21 as Apr 13, 2026.
Can I keep using the Hashicorp Vault 1.21 after its EOSL date?
Yes. EOSL means Hashicorp Vault stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Hashicorp Vault 1.21 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Hashicorp Vault 1.21
4 published CVEs affect the Hashicorp Vault 1.21, including 3 rated critical or high severity. Hashicorp Vault no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-3605 | HIGH | 8.1 | Apr 17, 2026 | An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. |
| CVE-2026-5807 | HIGH | 7.5 | Apr 17, 2026 | Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate operators from completing these workflows. This vulnerability, CVE-2026-5807, is fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0. |
| CVE-2026-4525 | HIGH | 7.5 | Apr 17, 2026 | If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16. |
| CVE-2026-5052 | MEDIUM | 5.3 | Apr 17, 2026 | Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. This may lead to these requests being sent to local network targets, potentially leading to information disclosure. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. |