Argo CD 3.6 · Version Status

Argo CD 3.6 End of Life Date

Argo CD 3.6 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.

✓ Argo CD 3.6 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
3.6.1
Standard release
Release Date
Nov 3, 2026
Argo CD 3.6 series
Where these dates come from
ReleaseNov 3, 2026Vendor's own page (our correction) · github.com · checked Nov 4, 2026medium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Argo CD 3.6 was released on November 3, 2026 and has no published end-of-life date yet. Its most recent patch is 3.6.1, published November 4, 2026.

← Argo CD 3.5 All Argo CD versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/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 →
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 3.6 end of life mean?

When Argo CD 3.6 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 Argo CD 3.6 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does Argo CD 3.6 reach end of life?
Argo CD 3.6 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Argo CD 3.6 still supported?
Yes, Argo CD 3.6 is currently supported. The EOL date is TBD.
What should I upgrade to from Argo CD 3.6?
The recommended upgrade from Argo CD 3.6 is Argo CD 3.6 — the latest actively supported version. Check the Argo CD full timeline for all supported versions.
What are the security risks of running Argo CD 3.6 past EOL?
When Argo CD 3.6 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 Argo CD should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →