Skip to content
Fencer Vulns
critical 9.9

CVE-2026-113708 json

Argo CD: A Kustomize remote ref 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-113708 , EUVD-2026-105249

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

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.7.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, Kustomize passes ref or version query values from remote resource, base, or component URLs to git fetch without an end-of-options separator. A leading-hyphen value can be parsed as --upload-pack and execute a command inside argocd-repo-server when the remote uses a local transport such as file://. Git does not run the supplied command for an https:// remote. The local transport does not leave the pod, so blocking repo-server egress does not prevent the execution. The command runs as the repo-server user, can read repository credentials and other process-accessible data, and can return output through manifest-generation errors. An attacker can commit a Kustomization to a Git repository that an Application builds or upload 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. Kustomize 5.0.0 introduced acceptance of file://, whereas 4.5.7 rejects that transport; replacing the affected Kustomize with a newer version alone does not correct the missing option separator. 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-113708 updated cvss 9.9

github.com/argoproj/argo-cd/v3: github.com/argoproj/argo-cd/v2: argo-cd: A Kustomize remote ref 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
19 d ago

Exploit prediction

0.67% chance of exploitation in the next 30 days, higher than 52% 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.7.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-88 Improper Neutralization of Argument Delimiters in a Command

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.