Nomad End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Nomad versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.12 | 0.12.12 | Jul 9, 2020 | Nov 15, 2021 | 1681 days past EOL | EOL |
| 1.0 | 1.0.18 | Dec 8, 2020 | May 11, 2022 | 1504 days past EOL | EOL |
| 1.1 | 1.1.18 | May 17, 2021 | Oct 4, 2022 | 1358 days past EOL | EOL |
| 1.2 | 1.2.16 | Nov 15, 2021 | Mar 1, 2023 | 1210 days past EOL | EOL |
| 1.3 | 1.3.16 | May 11, 2022 | Jul 18, 2023 | 1071 days past EOL | EOL |
| 1.4 | 1.4.14 | Oct 4, 2022 | Dec 7, 2023 | 929 days past EOL | EOL |
| 1.5 | 1.5.17 | Mar 1, 2023 | May 28, 2024 | 756 days past EOL | EOL |
| 1.6 | 1.6.10 | Jul 18, 2023 | Oct 10, 2024 | 621 days past EOL | EOL |
| 1.7 | 1.7.7 | Dec 7, 2023 | Apr 9, 2025 | 440 days past EOL | EOL |
| 1.8 | 1.8.4 | May 28, 2024 | Nov 11, 2025 | 224 days past EOL | EOL |
| 1.9 | 1.9.7 | Oct 10, 2024 | Apr 21, 2026 | 63 days past EOL | EOL |
| 1.10 | 1.10.5 | Apr 9, 2025 | TBD | Supported | Active |
| 1.11 | 1.11.3 | Nov 11, 2025 | TBD | Supported | Active |
| 2.0 | 2.0.3 | Apr 21, 2026 | TBD | Supported | Active |
What does Nomad end of life mean for your organization?
When a version of Nomad 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 Nomad 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Nomad versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →