# CVE-2026-62185: Argo CD Helm Chart < 10.0.0 Missing Network Policy RCE

> Missing default network policies in Argo CD Helm Chart allow cluster-wide access to internal APIs, enabling remote code execution and cluster compromise.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-25jf-qr89-v245

## What is CVE-2026-62185?

CVE-2026-62185 is a high-severity vulnerability in argoproj argo-helm, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-62185?


## How do I fix CVE-2026-62185?

No fix has been published for CVE-2026-62185 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62185 being exploited?

There is no known exploitation of CVE-2026-62185 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62185 and fix it if it is affected.

What it is: CVE-2026-62185 is a high-severity vulnerability in argoproj argo-helm, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62185 in the wild and no public exploit code.

Affected product: argoproj argo-helm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62185/ (Markdown: https://insights.sbomify.com/CVE-2026-62185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62185
- OSV: https://osv.dev/vulnerability/CVE-2026-62185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62185/
Summaries are generated and may contain mistakes; the official description above is the record.