CVE-2026-62185
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedArgo CD Helm Chart before 10.0.0 fails to install network policies by default, allowing any pod on a cluster to access repo-server and other Argo APIs. Attackers can exploit this unrestricted network access through combined attacks to achieve cluster compromise and remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Argo CD Helm Chart before version 10.0.0 does not install network policies by default, resulting in unrestricted pod-to-pod network communication within the cluster. This allows any pod to reach the repo-server and other Argo CD API endpoints that should normally be protected. Attackers who gain initial access to any pod can exploit this open network access to reach sensitive components and potentially achieve cluster compromise and remote code execution through combined attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Argo CD Helm Chart versionRun `helm list -n <namespace>` or `helm list -A` to list deployed Helm releases. Identify the Argo CD release and check the version or revision. If using Argo CD as a built-in cluster add-on, consult your cluster management tooling for the chart version.Affected if The chart version is before 10.0.0
-
Check network policy Helm valueRun `helm get values <release-name> -n <namespace>` to retrieve the deployed values, or inspect your Helm values YAML file. Look for the `networkPolicy.enabled` setting.Affected if networkPolicy.enabled is absent, set to false, or not explicitly configured to true
-
Verify NetworkPolicy resources existRun `kubectl get networkpolicies -n <argo-cd-namespace>` to list all NetworkPolicy resources in the namespace where Argo CD is deployed.Affected if No NetworkPolicy resources are present, or policies do not restrict pod-to-pod communication to Argo CD components only
-
Inspect network policy rulesRun `kubectl get networkpolicy <policy-name> -n <argo-cd-namespace> -o yaml` to examine the ingress and egress rules defined in each policy.Affected if The policies allow unrestricted pod-to-pod ingress/egress or do not specifically limit communication to known Argo CD component ports
You are affected if the Argo CD Helm Chart version is below 10.0.0 and network policies are not enabled or not properly restricting pod-to-pod communication within the cluster.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable network policies in the Argo CD Helm Chart by setting the networkPolicy.enabled value to true, or upgrade to version 10.0.0+ which should include network policies enabled by default. After enabling, verify that legitimate Argo CD component communication is still functional.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62185 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data