Argo Cd 2.13 · Version Status
Argo Cd 2.13 End of Life Date
Argo Cd 2.13 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Argo Cd 2.13 is past end of life. This version no longer receives security patches. 269 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 13, 2025
269 days past EOL
Latest Release
2.13.9
Standard release
Release Date
Nov 4, 2024
Argo Cd 2.13 series
| Version | Latest | EOL Date | Status |
|---|
| 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 2.13 end of life mean?
When Argo Cd 2.13 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 2.13 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 2.13 reach end of life?
Argo Cd 2.13 reached end of life on August 13, 2025. This version is no longer receiving security patches.
Is Argo Cd 2.13 still supported?
No. Argo Cd 2.13 reached end of life on August 13, 2025 and is no longer receiving security patches.
What should I upgrade to from Argo Cd 2.13?
The recommended upgrade from Argo Cd 2.13 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 2.13 past EOL?
When Argo Cd 2.13 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.