Nomad 1.6 · Version Status
Nomad 1.6 End of Life Date
Nomad 1.6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Nomad 1.6 is past end of life. This version no longer receives security patches. 576 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 10, 2024
576 days past EOL
Latest Release
1.6.10
Standard release
Release Date
Jul 18, 2023
Nomad 1.6 series
| Version | Latest | EOL Date | Status |
|---|
| 0.12 |
0.12.12 |
Nov 15, 2021 |
EOL |
| 1.0 |
1.0.18 |
May 11, 2022 |
EOL |
| 1.1 |
1.1.18 |
Oct 4, 2022 |
EOL |
| 1.2 |
1.2.16 |
Mar 1, 2023 |
EOL |
| 1.3 |
1.3.16 |
Jul 18, 2023 |
EOL |
| 1.4 |
1.4.14 |
Dec 7, 2023 |
EOL |
| 1.5 |
1.5.17 |
May 28, 2024 |
EOL |
| → 1.6 |
1.6.10 |
Oct 10, 2024 |
EOL |
What does Nomad 1.6 end of life mean?
When Nomad 1.6 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Nomad 1.6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Nomad 2.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Nomad 1.6 reach end of life?
Nomad 1.6 reached end of life on October 10, 2024. This version is no longer receiving security patches.
Is Nomad 1.6 still supported?
No. Nomad 1.6 reached end of life on October 10, 2024 and is no longer receiving security patches.
What should I upgrade to from Nomad 1.6?
The recommended upgrade from Nomad 1.6 is
Nomad 2.0 — the latest actively supported version. Check the
Nomad full timeline for all supported versions.
What are the security risks of running Nomad 1.6 past EOL?
When Nomad 1.6 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Nomad should migrate immediately or implement compensating controls.