HashiCorp Boundary end of life: end of support by version
HashiCorp · Firewalls & Security
For HashiCorp Boundary by HashiCorp, patchletter knows 6 support cycles. 3 of them have already ended and receive no more security updates. The current version of HashiCorp Boundary is 0.21.3. The cycles come from the open endoflife.date project, last reconciled on 07/11/2026.
When does support end for which HashiCorp Boundary version?
A cycle is a maintained version line. Where a date is given, support ends on that day. After it the vendor ships no more security updates for that line.
| Cycle | Latest version | End of support | Status |
|---|---|---|---|
| 0.21 | 0.21.3 | no date on record | supported |
| 0.20 | 0.20.3 | no date on record | supported |
| 0.19 | 0.19.5 | no date on record | supported |
| 0.18 | 0.18.2 | 332 days ago | End of Life |
| 0.17 | 0.17.2 | 409 days ago | End of Life |
| 0.16 | 0.16.3 | 636 days ago | End of Life |
Which HashiCorp Boundary versions no longer receive security updates?
3 of 6 cycles have ended. If you run one of those lines, the vendor ships you no more patches, not even for critical flaws.
- HashiCorp Boundary 0.180.18.2
- HashiCorp Boundary 0.170.17.2
- HashiCorp Boundary 0.160.16.3
Where does the EOL data for HashiCorp Boundary come from?
From the open endoflife.date project, which collects vendors' official support commitments. patchletter reconciles the cycles daily; the HashiCorp Boundary data is as of 07/11/2026. In case of doubt the vendor's own lifecycle page applies. patchletter deliberately stores no vendor full texts.
New HashiCorp Boundary versions by email
Tick the product and patchletter reports new releases by email. The update email costs nothing, and one click stops it again. The warning 90, 30 and 7 days before support ends is part of patchletter Pro.