CVE-2026-113672 Argo CD: A Jsonnet import can read files from the repo-server
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-113672?
CVE-2026-113672 is a critical vulnerability in argoproj argo-cd, published on 20 Oct 2026.
Official description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 0.9.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, the repo-server evaluates .jsonnet files with an importer that does not confine import, importstr, or importbin to the repository root. Absolute paths, parent-directory traversal, and repository symlinks can open any file readable by the repo-server, including /proc/self/environ, projected service-account tokens, mounted private keys, and repository credentials. Although generated Secrets are redacted, placing imported contents in a ConfigMap returns the data to the caller. Using importstr on a non-terminating device such as /dev/zero can exhaust repo-server memory. An attacker can commit a .jsonnet file to a Git repository used by an Application or upload the file through POST /api/v1/applications/manifestsWithFiles, also exposed by argocd app diff --local --server-side-generate. Directory applications evaluate every .jsonnet file in the application directory. The upload path requires only Application get permission on an existing directory Application, without Application update or sync permission or repository write access. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
Weakness: CWE-22
Which versions are affected by CVE-2026-113672?
1 open source package ship an affected version, including argo-cd.
| Package | Affected | Fixed in |
|---|---|---|
argo-cd Bitnami | From 0.9.0 | 3.3.1, 3.4.10, 3.5.4 |
How do I fix CVE-2026-113672?
Upgrade argo-cd to a fixed version for your release line: 3.3.1, 3.4.10 or 3.5.4.
Is CVE-2026-113672 being exploited?
There is no known exploitation of CVE-2026-113672 in the wild and no public exploit code.
Sources
Also known as BIT-argo-cd-2026-113672.