CVE-2026-113672
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes
- Risk score
- 81/100
- CVSS
- 9.9 v3.1
- Exploit chance (30 days)
- 0.8%
- Published
- 20 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Argo CD has a vulnerability in its repo-server that allows an attacker to access any file readable by the server, potentially leading to sensitive data exposure and memory exhaustion.
- Affected
- {'products': ['Argo CD'], 'packages': [], 'versions': ['0.9.0', '3.3.15', '3.4.10', '3.5.4', '3.6.0-rc2']}
- Fix
- Upgrade to version 3.3.16 or later, or 3.4.11 or later, or 3.5.5 or later, or 3.6.0 or later.
- Exploitation
- No known exploitation
Not confirmed. 3.3.16, 3.4.11, 3.5.5 isn't in the advisory. Check the vendor's advisory before acting on this.
Why it is Red
- CVSS 9.9 critical
- On your watchlist: kubernetes
References
- https://argo-cd.readthedocs.io/en/stable/user-guide/tool_detection/#disable-built-in-tools
- https://github.com/argoproj/argo-cd/commit/27471d524958878e7acc5131fb466b292079cd05
- https://github.com/argoproj/argo-cd/pull/561
- https://github.com/argoproj/argo-cd/releases/tag/v3.3.15
- https://github.com/argoproj/argo-cd/releases/tag/v3.4.10
- https://github.com/argoproj/argo-cd/releases/tag/v3.5.4
- https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-3v3m-wc6v-x4x3
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-6gcg-hp2x-q54h
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-m3vr-7329-44ww
Original 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.
Last activity 20 Oct 2026. Patch Forecast updates every hour.