Complete end-of-life dates, support windows, and security status for all Boundary versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.16 | 0.16.3 | Apr 30, 2024 | Feb 10, 2025 | 453 days past EOL | EOL |
| 0.17 | 0.17.2 | Jul 31, 2024 | Sep 25, 2025 | 226 days past EOL | EOL |
| 0.18 | 0.18.2 | Oct 14, 2024 | Dec 11, 2025 | 149 days past EOL | EOL |
| 0.19 | 0.19.5 | Feb 10, 2025 | Already EOL | Supported | Active |
| 0.20 | 0.20.3 | Sep 25, 2025 | Already EOL | Supported | Active |
| 0.21 | 0.21.3 | Dec 11, 2025 | Already EOL | Supported | Active |
When a Boundary 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 Boundary 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 →