CVE-2026-113672: Argo CD Jsonnet imports read any file in repo-server, including credentials

Critical 9.9 EPSS 0.8%

Argo CD evaluates .jsonnet files in argocd-repo-server with an importer that does not confine import, importstr or importbin to the repository, so absolute paths, ../ traversal or symlinks can read any file the repo-server can read, such as /proc/self/environ, the service-account token, mounted private keys and repository credentials (returned by placing them in a ConfigMap). importstr of /dev/zero can also exhaust repo-server memory. An attacker needs to commit a .jsonnet file to a repository an Application builds, or only Application get permission on a directory Application to upload it via POST /api/v1/applications/manifestsWithFiles. Rated critical (CVSS 9.9) by the Argo CD maintainers.

CVE-2026-113672CVE identifier
9.9CVSS 3.1 base score (critical)
0.8%EPSS: chance of exploitation in the next 30 days (higher than 58% 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 and service-account tokens the repo-server could read.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.

Affected and fixed versions

Affected:

Argo CD v0.9.0 and later 0.x, 1.x and 2.x (no fix on those lines)
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"}'
kubectl -n argocd get cm argocd-cm -o jsonpath='{.data.jsonnet\.enable}{"\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

Set jsonnet.enable to "false" in the argocd-cm ConfigMap (kubectl -n argocd patch cm argocd-cm --type merge -p '{"data":{"jsonnet.enable":"false"}}'). Argo CD then skips .jsonnet files, both committed and uploaded; applications that depend on Jsonnet stop rendering those files.

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.