Nomad · Lifecycle Status

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.

Nomad 1.10.5 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.10.5
1.10 series
Next EOL
None upcoming
Active Versions
3
of 14 total
EOL Versions
11
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2021202220232024202520260.121.01.11.21.31.41.51.61.71.81.91.101.112.0TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
0.12 0.12.12 Jul 9, 2020 Nov 15, 2021 1636 days past EOL EOL
1.0 1.0.18 Dec 8, 2020 May 11, 2022 1459 days past EOL EOL
1.1 1.1.18 May 17, 2021 Oct 4, 2022 1313 days past EOL EOL
1.2 1.2.16 Nov 15, 2021 Mar 1, 2023 1165 days past EOL EOL
1.3 1.3.16 May 11, 2022 Jul 18, 2023 1026 days past EOL EOL
1.4 1.4.14 Oct 4, 2022 Dec 7, 2023 884 days past EOL EOL
1.5 1.5.17 Mar 1, 2023 May 28, 2024 711 days past EOL EOL
1.6 1.6.10 Jul 18, 2023 Oct 10, 2024 576 days past EOL EOL
1.7 1.7.7 Dec 7, 2023 Apr 9, 2025 395 days past EOL EOL
1.8 1.8.4 May 28, 2024 Nov 11, 2025 179 days past EOL EOL
1.9 1.9.7 Oct 10, 2024 Apr 21, 2026 18 days past EOL EOL
1.10 1.10.5 Apr 9, 2025 Already EOL Supported Active
1.11 1.11.3 Nov 11, 2025 Already EOL Supported Active
2.0 2.0.0 Apr 21, 2026 Already EOL Supported Active

What does Nomad end of life mean for your organization?

When a Nomad 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 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Nomad?
See the full table above for all Nomad version EOL dates.
What is the latest supported version of Nomad?
The latest active version of Nomad is 1.10.5. Always verify against the table above as support windows can change.
What happens when Nomad reaches end of life?
When Nomad reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Nomad?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Nomad versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →