Skip to content
Fencer Vulns
critical 9.9

CVE-2026-113709 json

Argo CD: A Kustomize Helm config home can run commands in the repo-server

published 2026-10-20 19 d ago modified 2026-10-29 11 d ago also BIT-argo-cd-2026-113709 , EUVD-2026-105250

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami argo-cd 3.3.15, 3.4.10, 3.5.4
  • linuxfoundation argo_continuous_delivery 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2
  • linuxfoundation argo-cd 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-113709 updated cvss 9.9

github.com/argoproj/argo-cd/v3: github.com/argoproj/argo-cd/v2: argo-cd: argocd: A Kustomize Helm config home can run commands in the repo-server

  • Red Hat Openshift Data Foundation 4 odf4/odf-multicluster-rhel9-operator Red Hat OpenShift GitOps openshift-gitops-1/argocd-rhel9, openshift-gitops-1/gitops-rhel9, openshift-gitops-1/argocd-agent-rhel9, openshift-gitops-1/gitops-rhel9-operator, openshift-gitops-1/argocd-image-updater-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 d ago

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OSV 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami argo-cd
>=2.1.0, <3.3.15
>=3.4.0, <3.4.10
>=3.5.0, <3.5.4
3.3.15
3.4.10
3.5.4

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.