Complete end-of-life dates, support windows, and security status for all Hashicorp Vault versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.9 | 1.9.10 | Nov 16, 2021 | Oct 10, 2022 | 1307 days past EOL | EOL |
| 1.10 | 1.10.11 | Mar 21, 2022 | Mar 1, 2023 | 1165 days past EOL | EOL |
| 1.11 | 1.11.12 | Jun 17, 2022 | Jun 21, 2023 | 1053 days past EOL | EOL |
| 1.12 | 1.12.11 | Oct 10, 2022 | Sep 27, 2023 | 955 days past EOL | EOL |
| 1.13 | 1.13.13 | Mar 1, 2023 | Mar 25, 2024 | 775 days past EOL | EOL |
| 1.14 | 1.14.10 | Jun 19, 2023 | Jun 10, 2024 | 698 days past EOL | EOL |
| 1.15 | 1.15.6 | Sep 22, 2023 | Oct 8, 2024 | 578 days past EOL | EOL |
| 1.16 LTS | 1.16.3 | Mar 25, 2024 | Jun 10, 2024 | 698 days past EOL | EOL |
| 1.17 | 1.17.6 | Jun 10, 2024 | Oct 9, 2024 | 577 days past EOL | EOL |
| 1.18 | 1.18.5 | Oct 8, 2024 | Mar 4, 2025 | 431 days past EOL | EOL |
| 1.19 LTS | 1.19.5 | Mar 4, 2025 | Jun 23, 2025 | 320 days past EOL | EOL |
| 1.20 | 1.20.4 | Jun 23, 2025 | Oct 21, 2025 | 200 days past EOL | EOL |
| 1.21 | 1.21.4 | Oct 21, 2025 | Apr 13, 2026 | 26 days past EOL | EOL |
| 2.0 | 2.0.0 | Apr 13, 2026 | Already EOL | Supported | Active |
When a Hashicorp Vault version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Hashicorp Vault should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →