Argo Cd 1.0 · Version Status

Argo Cd 1.0 End of Life Date

Argo Cd 1.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Argo Cd 1.0 is past end of life. This version no longer receives security patches. 2369 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 13, 2019
2369 days past EOL
Latest Release
1.0.2
Standard release
Release Date
May 16, 2019
Argo Cd 1.0 series
All Argo Cd versions Argo Cd 1.1 →
Recommended upgrade path
Argo Cd 3.3
Latest release: 3.3.9 · EOL: Supported
View full Argo Cd timeline →
All Argo Cd Versions
VersionLatestEOL DateStatus
1.0 1.0.2 Nov 13, 2019 EOL
1.1 1.1.2 Jan 18, 2020 EOL
1.2 1.2.5 Jan 18, 2020 EOL
1.3 1.3.6 Jun 17, 2020 EOL
1.4 1.4.3 Aug 26, 2020 EOL
1.5 1.5.8 Dec 10, 2020 EOL
1.6 1.6.2 Dec 15, 2021 EOL
1.7 1.7.14 Aug 20, 2021 EOL

What does Argo Cd 1.0 end of life mean?

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

Migrate to Argo Cd 3.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

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