← ← Back to all products
Hashicorp Boundary
Active
DevOps & CI/CD Latest Version: 0.21.3 Latest Release: Apr 30, 2026
HashiCorp Boundary provides simple and secure remote access to dynamic hosts and services.
Versions
6
Latest Version
0.21.3
Active Support
3
EOL
3
Lifecycle Timeline
Today ↓
0.21
0.21
0.20
0.20
0.19
0.19
0.18
0.18
0.17
0.17
0.16
0.16
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 0.21 | Dec 11, 2025 | Yes | No | 0.21.3 | No | Active |
| 0.20 | Sep 25, 2025 | Yes | No | 0.20.3 | No | Active |
| 0.19 | Feb 10, 2025 | Yes | No | 0.19.5 | No | Active |
| 0.18 | Oct 14, 2024 | No | Dec 11, 2025 | 0.18.2 | No | EOL |
| 0.17 | Jul 31, 2024 | No | Sep 25, 2025 | 0.17.2 | No | EOL |
| 0.16 | Apr 30, 2024 | No | Feb 10, 2025 | 0.16.3 | No | EOL |
Frequently Asked Questions
Which versions of Hashicorp Boundary have reached end of life?
The following Hashicorp Boundary versions have reached end of life and no longer receive security updates: 0.18, 0.17, 0.16. It is recommended to upgrade to a supported version.
Is it safe to continue using Hashicorp Boundary 0.18?
Hashicorp Boundary 0.18 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Hashicorp Boundary?
The latest version of Hashicorp Boundary is 0.21.3, released in the 0.21 release cycle.
How many versions of Hashicorp Boundary are currently supported?
Hashicorp Boundary currently has 3 actively supported version(s): 0.21, 0.20, 0.19.
When does Hashicorp Boundary 0.21 reach end of life?
Hashicorp Boundary 0.21 does not have a specific end-of-life date announced yet.
What should I do when Hashicorp Boundary reaches end of life?
When a Hashicorp Boundary version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.