Hashicorp Vault End of Life Dates
other
Developers rely on secure and reliable tools to manage sensitive data, and Hashicorp Vault has been a trusted solution since its creation. Maintained by Hashicorp, a leading provider of infrastructure automation tools, Vault has been widely adopted for its ability to securely store and manage secrets, certificates, and other sensitive information. With a strong focus on security and compliance, Hashicorp continues to update and improve Vault, ensuring it remains a top choice for developers who need to protect their applications and data.
The end-of-life landscape for Hashicorp Vault is relatively straightforward, with a total of 14 versions released to date. Of these, 13 versions have already reached their end-of-life, with the most recent being version 1.21, which expired on 2026-04-13. Currently, only one version remains actively supported, providing developers with a clear and stable platform for their applications. With no next end-of-life date announced, developers can focus on their current projects without worrying about imminent support deadlines. The latest stable version, 2.0.2, is the recommended choice for new projects and upgrades.
From a security perspective, Hashicorp Vault has an impressive track record, with no known CVEs currently tracked. This means that there are no critical vulnerabilities that require immediate attention, giving developers peace of mind when using Vault to manage their sensitive data. As a result, there is no most affected version, and no action is required to address specific security concerns. With its strong security foundation and active maintenance, Hashicorp Vault remains a reliable choice for developers who need to securely manage their applications and data, and by tracking its end-of-life dates and supported versions, they can ensure their projects remain secure and up-to-date.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2.1 | Aug 31, 2026 | — | No | — | 2.1.0 | — | Active | |
| 2.0 | Apr 13, 2026 | — | Aug 31, 2026 | 7d ago | 2.0.4 | — | EOL | |
| 1.21 | Oct 21, 2025 | — | Apr 13, 2026 | 147d ago | 1.21.4 | — | EOL | |
| 1.20 | Jun 23, 2025 | — | Oct 21, 2025 | 321d ago | 1.20.4 | — | EOL | |
| 1.19 LTS | Mar 4, 2025 | — | Jun 23, 2025 | 441d ago | 1.19.5 | — | EOL | |
| 1.18 | Oct 8, 2024 | — | Mar 4, 2025 | 552d ago | 1.18.5 | — | EOL | |
| 1.17 | Jun 10, 2024 | — | Oct 9, 2024 | 698d ago | 1.17.6 | — | EOL | |
| 1.16 LTS | Mar 25, 2024 | — | Jun 10, 2024 | 819d ago | 1.16.3 | — | EOL | |
| 1.15 | Sep 22, 2023 | — | Oct 8, 2024 | 699d ago | 1.15.6 | — | EOL | |
| 1.14 | Jun 19, 2023 | — | Jun 10, 2024 | 819d ago | 1.14.10 | — | EOL | |
| 1.13 | Mar 1, 2023 | — | Mar 25, 2024 | 896d ago | 1.13.13 | — | EOL | |
| 1.12 | Oct 10, 2022 | — | Sep 27, 2023 | 1076d ago | 1.12.11 | — | EOL | |
| 1.11 | Jun 17, 2022 | — | Jun 21, 2023 | 1174d ago | 1.11.12 | — | EOL | |
| 1.10 | Mar 21, 2022 | — | Mar 1, 2023 | 1286d ago | 1.10.11 | — | EOL | |
| 1.9 | Nov 16, 2021 | — | Oct 10, 2022 | 1428d ago | 1.9.10 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
