Containerd · Lifecycle Status

Containerd End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Containerd versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Containerd 1.7 reaches end of life on September 1, 2026. Plan your migration now — 115 days remaining.
Latest Active
2.0.8
2.0 series
Next EOL
1.7
Sep 1, 2026
Active Versions
3
of 12 total
EOL Versions
8
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201820192020202120222023202420252026202720281.01.11.21.31.41.51.61.72.02.12.22.3TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.0 1.0.3 Dec 5, 2017 Dec 5, 2018 2712 days past EOL EOL
1.1 1.1.8 Apr 23, 2018 Oct 23, 2019 2390 days past EOL EOL
1.2 1.2.14 Oct 24, 2018 Oct 15, 2020 2032 days past EOL EOL
1.3 1.3.10 Sep 26, 2019 Mar 4, 2021 1892 days past EOL EOL
1.4 1.4.13 Aug 17, 2020 Mar 3, 2022 1528 days past EOL EOL
1.5 1.5.18 May 3, 2021 Feb 28, 2023 1166 days past EOL EOL
1.6 LTS 1.6.39 Feb 15, 2022 Aug 23, 2025 259 days past EOL EOL
1.7 LTS 1.7.31 Mar 10, 2023 Sep 1, 2026 115 days remaining Warning
2.0 LTS 2.0.8 Nov 5, 2024 Mar 1, 2027 296 days remaining Active
2.1 2.1.7 May 7, 2025 May 5, 2026 4 days past EOL EOL
2.2 2.2.3 Nov 5, 2025 Nov 6, 2026 181 days remaining Active
2.3 LTS 2.3.0 Apr 30, 2026 Apr 30, 2028 722 days remaining Active

What does Containerd end of life mean for your organization?

When a Containerd 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 Containerd 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 Containerd?
The next Containerd version reaching EOL is 1.7 on September 1, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Containerd?
The latest active version of Containerd is 2.0.8. Always verify against the table above as support windows can change.
What happens when Containerd reaches end of life?
When Containerd 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 Containerd?
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 Containerd 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 →