Etcd 3.0 · Version Status
Etcd 3.0 End of Life Date
Etcd 3.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Etcd 3.0 is past end of life. This version no longer receives security patches. 3396 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 20, 2017
3396 days past EOL
Latest Release
3.0.17
Standard release
Release Date
Jun 30, 2016
Etcd 3.0 series
| Version | Latest | EOL Date | Status |
|---|
| → 3.0 |
3.0.17 |
Jan 20, 2017 |
EOL |
| 3.1 |
3.1.20 |
Oct 10, 2018 |
EOL |
| 3.2 |
3.2.32 |
Mar 28, 2021 |
EOL |
| 3.3 |
3.3.27 |
Oct 15, 2021 |
EOL |
| 3.4 |
3.4.44 |
May 15, 2025 |
EOL |
| 3.5 |
3.5.30 |
EOL |
Active |
| 3.6 |
3.6.11 |
EOL |
Active |
What does Etcd 3.0 end of life mean?
When Etcd 3.0 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 Etcd 3.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Etcd 3.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Etcd 3.0 reach end of life?
Etcd 3.0 reached end of life on January 20, 2017. This version is no longer receiving security patches.
Is Etcd 3.0 still supported?
No. Etcd 3.0 reached end of life on January 20, 2017 and is no longer receiving security patches.
What should I upgrade to from Etcd 3.0?
The recommended upgrade from Etcd 3.0 is
Etcd 3.6 — the latest actively supported version. Check the
Etcd full timeline for all supported versions.
What are the security risks of running Etcd 3.0 past EOL?
When Etcd 3.0 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 Etcd should migrate immediately or implement compensating controls.