containerd 1.7 · Version Status
containerd 1.7 End of Life Date
containerd 1.7 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 1.7 is past end of life. This version no longer receives security patches. 8 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 1, 2026
8 days past EOL
Latest Release
1.7.35
LTS release
Release Date
Mar 10, 2023
containerd 1.7 series
Lifecycle detail
containerd 1.7 was released on March 10, 2023 and support ended on September 1, 2026 — a supported lifespan of 3 years and 6 months, in line with the 3 years and 6 months median for containerd LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 1.7.35, published September 4, 2026 — 3 days after the published end-of-life date. It has been without security patches for 8 days.
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 →
Extended Support
Extended containerd 1.7 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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 1.7 end of life mean?
When containerd 1.7 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 1.7 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to containerd 2.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does containerd 1.7 reach end of life?
containerd 1.7 reached end of life on September 1, 2026. This version is no longer receiving security patches.
Is containerd 1.7 still supported?
No. containerd 1.7 reached end of life on September 1, 2026 and is no longer receiving security patches.
What should I upgrade to from containerd 1.7?
The recommended upgrade from containerd 1.7 is
containerd 2.3 — the latest actively supported version. Check the
containerd full timeline for all supported versions.
What are the security risks of running containerd 1.7 past EOL?
When containerd 1.7 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.