Caddy 1 · Version Status

Caddy 1 End of Life Date

Caddy 1 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.

Caddy 1 is past end of life. This version no longer receives security patches. 2275 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 1, 2020
2275 days past EOL
Latest Release
1.0.5
Standard release
Release Date
Apr 24, 2019
Caddy 1 series
Lifecycle detail

Caddy 1 was released on April 24, 2019 and support ended on July 1, 2020 — a supported lifespan of 1 year and 2 months. The last patch it will ever receive is 1.0.5, published February 28, 2020 — 4 months before support ended. It has been without security patches for 6 years and 3 months.

All Caddy versions Caddy 2 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
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 →
Recommended upgrade path
Caddy 2
Latest release: 2.11.4 · EOL: Supported
View full Caddy timeline →
Extended Support
Extended Caddy 1 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Caddy Versions
VersionLatestEOL DateStatus
1 1.0.5 Jul 1, 2020 EOL
2 2.11.4 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Caddy 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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 vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Caddy should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →