CVE-2026-113709
CRITICALDescription
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 requires only Application get permission on an existing Application, without Application update or sync permission or repository write access. Both delivery paths require prior operator enablement of --enable-helm; deployments that do not enable it are not affected. Kustomize 4.1.0 first passed helmGlobals.configHome through to Helm. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 36% of all known CVEs.
References
Related Vulnerabilities
Other CWE-829 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-17246 | Critical | 9.8 | 82% | - | Fix |
| CVE-2024-5762 | High | 8.1 | 72% | - | - |
| CVE-2026-0770 | Critical | 9.8 | 63% | KEV | - |
| CVE-2018-7422 | High | 7.5 | 62% | - | - |
| CVE-2023-2249 | High | 8.8 | 61% | - | - |
| CVE-2025-32463 | Critical | 9.3 | 55% | KEV | Fix |
Common questions
How do I fix CVE-2026-113709?
No published fix for CVE-2026-113709 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-113709 being actively exploited?
Not that we know of. CVE-2026-113709 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.42% is the estimated probability that it will be exploited in the next 30 days. That is higher than 36% of all scored CVEs.
How severe is CVE-2026-113709?
CVE-2026-113709 has a CVSS v3 base score of 9.9, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-113709
Markdown
[](https://tridentstack.com/cve/CVE-2026-113709)HTML
<a href="https://tridentstack.com/cve/CVE-2026-113709"><img src="https://tridentstack.com/cve/badge/CVE-2026-113709.svg" alt="CVE-2026-113709"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-21.