Critical-Severity Flaw in argoproj argo-cd Tracked as CVE-2026-113709
A newly published critical vulnerability in argoproj argo-cd carries a CVSS score of 9.9. Here is what is affected and how to respond.
Key points
- CVE-2026-113709 affects argoproj argo-cd.
- CVSS 9.9 (Critical).
- No exploitation confirmed yet.
argoproj argo-cd is affected by CVE-2026-113709, a security flaw that the National Vulnerability Database rates 9.9 out of 10.
At a glance
- CVE
- CVE-2026-113709
- Product
- argoproj argo-cd
- CVSS
- 9.9 Critical
- Weakness
- CWE-829
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.1.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, when an operator has enabled --enable-helm for kustomize build, helmGlobals.configHome can point Helm's config and data directories at a repository-controlled location. Helm automatically loads a downloader plugin from `<configHome>/.data/plugins` without a separate plugin-install step and executes its program inside argocd-repo-server when a helmCharts repository URL uses the plugin's protocol. The command runs as the repo-server user and can read repository credentials and other process-accessible data. An attacker can commit the Kustomization and plugin to a Git repository that an Application builds or upload the files through POST /api/v1/applications/manifestsWithFiles, also exposed by argocd app diff --local --server-side-generate. The upload path require
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Argoproj | argo-cd | >= 2.1.0, < 3.3.15, >= 3.4.0-rc1, < 3.4.10, >= 3.5.0-rc1, < 3.5.4, >= 3.6.0-rc1, < 3.6.0-rc2 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-113709
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-113709?
CVE-2026-113709 is a CWE-829 vulnerability in argoproj argo-cd.
How severe is CVE-2026-113709?
It has a CVSS score of 9.9 Critical.
Is CVE-2026-113709 being exploited?
There is no public confirmation of exploitation at the time of publication.
