CVE-2026-62185
Argo CD Helm chart (<10.0.0) omits network policies, allowing pods to reach repo-server.
Is CVE-2026-62185 being exploited?
Not confirmed. CVE-2026-62185 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-62185?
CVE-2026-62185 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62185?
Yes. A fix has been recorded for CVE-2026-62185. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62185 affect?
CVE-2026-62185 affects Argo CD Helm chart < 10.0.0, repo-server, Argo CD APIs, Kubernetes clusters. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62185?
Upgrade Argo CD Helm chart to >=10.0.0 and enforce network policies restricting repo-server.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Any pod can access repo-server and Argo APIs, enabling attacker pivot to cluster compromise and remote code execution.
Immediate action required
- affected< 10.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.