Docker Engine 17.05 · Version Status
Docker Engine 17.05 End of Life Date
Docker Engine 17.05 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Docker Engine 17.05 is past end of life. This version no longer receives security patches. 3302 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 28, 2017
3302 days past EOL
Latest Release
17.05.0
Standard release
Release Date
May 4, 2017
Docker Engine 17.05 series
Lifecycle detail
Docker Engine 17.05 was released on May 4, 2017 and support ended on July 28, 2017 — a supported lifespan of 3 months, in line with the 3 months median for Docker Engine releases. The last patch it will ever receive is 17.05.0, published May 4, 2017 — 3 months before support ended. It has been without security patches for 9 years and 1 month. 22 newer Docker Engine releases have shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in CISA 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 Docker Engine 17.05 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Docker Engine Versions
| Version | Latest | EOL Date | Status |
|---|
| 17.03 |
17.03.2 |
May 5, 2017 |
EOL |
| 17.04 |
17.04.0 |
Jun 4, 2017 |
EOL |
| → 17.05 |
17.05.0 |
Jul 28, 2017 |
EOL |
| 17.06 |
17.06.2 |
Sep 29, 2017 |
EOL |
| 17.07 |
17.07.0 |
Oct 26, 2017 |
EOL |
| 17.09 |
17.09.1 |
Nov 17, 2017 |
EOL |
| 17.10 |
17.10.0 |
Dec 20, 2017 |
EOL |
| 17.11 |
17.11.0 |
Jan 27, 2018 |
EOL |
What does Docker Engine 17.05 end of life mean?
When Docker Engine 17.05 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 Docker Engine 17.05 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Docker Engine 29 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Docker Engine 17.05 reach end of life?
Docker Engine 17.05 reached end of life on July 28, 2017. This version is no longer receiving security patches.
Is Docker Engine 17.05 still supported?
No. Docker Engine 17.05 reached end of life on July 28, 2017 and is no longer receiving security patches.
What should I upgrade to from Docker Engine 17.05?
The recommended upgrade from Docker Engine 17.05 is
Docker Engine 29 — the latest actively supported version. Check the
Docker Engine full timeline for all supported versions.
What are the security risks of running Docker Engine 17.05 past EOL?
When Docker Engine 17.05 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 Docker Engine should migrate immediately or implement compensating controls.