CVE-2026-113708: Argo CD Kustomize remote ref option injection runs commands in repo-server

Critical 9.9 EPSS 0.7%

When Argo CD builds a Kustomization, Kustomize passes the ref or version value of a remote resource, base or component URL to git fetch without a '--' separator, so a value such as --upload-pack=<command> with a file:// remote runs that command inside argocd-repo-server. The command runs as the repo-server user, can read repository credentials, and its output comes back in the manifest-generation error. An attacker only needs to commit a Kustomization to a Git repository an Application builds, or Application get permission to upload files via POST /api/v1/applications/manifestsWithFiles. Rated critical (CVSS 9.9) by the Argo CD maintainers.

CVE-2026-113708CVE identifier
9.9CVSS 3.1 base score (critical)
0.7%EPSS: chance of exploitation in the next 30 days (higher than 52% of CVEs)
2026-10-20published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run the affected software and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
The Argo CD Deployments (including argocd-repo-server) roll out new pods automatically. Consider rotating repository credentials if untrusted users could commit Kustomizations or had Application get access.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.

Affected and fixed versions

Affected:

Argo CD v2.7.0 and later 2.x (no 2.x fix)
Argo CD 3.0.0 up to (not including) 3.3.15
Argo CD 3.4.0 up to (not including) 3.4.10
Argo CD 3.5.0 up to (not including) 3.5.4
Argo CD 3.6.0-rc1

Fixed in:

Argo CD v3.3.15
Argo CD v3.4.10
Argo CD v3.5.4
Argo CD v3.6.0-rc2

Am I affected?

argocd version
kubectl -n argocd get deploy argocd-repo-server -o jsonpath='{.spec.template.spec.containers[0].image}{"\n"}'

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Docker images

# Manifest installs (non-HA); pick the fixed tag for your line: v3.5.4, v3.4.10 or v3.3.15
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.5.4/manifests/install.yaml
# HA installs:
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.5.4/manifests/ha/install.yaml
# Helm (argo/argo-cd chart): upgrade the chart, or pin the image tag
helm repo update
helm upgrade argocd argo/argo-cd -n argocd --reuse-values --set global.image.tag=v3.5.4

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

There is no complete workaround besides upgrading.
Partial: pin every Application that runs Kustomize to a Kustomize older than 5.0 (for example 4.5.7) registered via kustomize.path.<version> in argocd-cm and spec.source.kustomize.version on each Application; Kustomize 5.x must not remain the default or another registered version.
Blocking repo-server egress does not help (file:// never leaves the pod); restricting Application get or blocking POST /api/v1/applications/manifestsWithFiles closes only the upload path.

Related vulnerabilities

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.