containerd 2.4 · Version Status
containerd 2.4 End of Life Date
containerd 2.4 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
containerd 2.4 is actively supported. EOL date: May 15, 2027.
📅 Get reminded before containerd 2.4 reaches EOL on May 15, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
May 15, 2027
240 days remaining
Latest Release
2.4.0
Standard release
Release Date
Sep 15, 2026
containerd 2.4 series
Lifecycle detail
containerd 2.4 was released on September 15, 2026 and support is scheduled to end on May 15, 2027 — a planned supported lifespan of 8 months, shorter than the 1 year and 7 months median for containerd releases. It is not an LTS release; containerd reserves longer patch windows for its LTS versions. Its most recent patch is 2.4.0, published September 16, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.3 |
Dec 5, 2018 |
EOL |
| 1.1 |
1.1.8 |
Oct 23, 2019 |
EOL |
| 1.2 |
1.2.14 |
Oct 15, 2020 |
EOL |
| 1.3 |
1.3.10 |
Mar 4, 2021 |
EOL |
| 1.4 |
1.4.13 |
Mar 3, 2022 |
EOL |
| 1.5 |
1.5.18 |
Feb 28, 2023 |
EOL |
| 1.6 LTS |
1.6.39 |
Aug 23, 2025 |
EOL |
| 1.7 LTS |
1.7.35 |
Sep 1, 2026 |
EOL |
What does containerd 2.4 end of life mean?
When containerd 2.4 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 containerd 2.4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to containerd 2.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does containerd 2.4 reach end of life?
containerd 2.4 reached end of life on May 15, 2027. That is 240 days remaining.
Is containerd 2.4 still supported?
Yes, containerd 2.4 is currently supported. The EOL date is May 15, 2027.
What should I upgrade to from containerd 2.4?
The recommended upgrade from containerd 2.4 is
containerd 2.4 — the latest actively supported version. Check the
containerd full timeline for all supported versions.
What are the security risks of running containerd 2.4 past EOL?
When containerd 2.4 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 containerd should migrate immediately or implement compensating controls.