Caddy 1 · Version Status

Caddy 1 End of Life Date

Caddy 1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Caddy 1 is past end of life. This version no longer receives security patches. 2138 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 1, 2020
2138 days past EOL
Latest Release
1.0.5
Standard release
Release Date
Apr 24, 2019
Caddy 1 series
All Caddy versions Caddy 2 →
Recommended upgrade path
Caddy 2
Latest release: 2.11.2 · EOL: Supported
View full Caddy timeline →
All Caddy Versions
VersionLatestEOL DateStatus
1 1.0.5 Jul 1, 2020 EOL
2 2.11.2 EOL Active

What does Caddy 1 end of life mean?

When Caddy 1 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 Caddy 1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Caddy 2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Caddy 1 reach end of life?
Caddy 1 reached end of life on July 1, 2020. This version is no longer receiving security patches.
Is Caddy 1 still supported?
No. Caddy 1 reached end of life on July 1, 2020 and is no longer receiving security patches.
What should I upgrade to from Caddy 1?
The recommended upgrade from Caddy 1 is Caddy 2 — the latest actively supported version. Check the Caddy full timeline for all supported versions.
What are the security risks of running Caddy 1 past EOL?
When Caddy 1 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 Caddy should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →