Complete end-of-life dates, support windows, and security status for all Etcd versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.0 | 3.0.17 | Jun 30, 2016 | Jan 20, 2017 | 3396 days past EOL | EOL |
| 3.1 | 3.1.20 | Jan 20, 2017 | Oct 10, 2018 | 2768 days past EOL | EOL |
| 3.2 | 3.2.32 | Jun 9, 2017 | Mar 28, 2021 | 1868 days past EOL | EOL |
| 3.3 | 3.3.27 | Feb 1, 2018 | Oct 15, 2021 | 1667 days past EOL | EOL |
| 3.4 | 3.4.44 | Aug 30, 2019 | May 15, 2025 | 359 days past EOL | EOL |
| 3.5 | 3.5.30 | Jun 15, 2021 | Already EOL | Supported | Active |
| 3.6 | 3.6.11 | May 15, 2025 | Already EOL | Supported | Active |
When a Etcd 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 Etcd 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →