Back to feed
21Track

argoproj argo-cd: Argo CD: A Jsonnet import can read files from the repo-server

argoproj argo-cd · CVE-2026-113672 EUVD-2026-105227
0 news outlets0 CERTs and agencies0 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable no, technical impact total, deployment low.

What is it?

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 versi

Evidence

No coverage recorded yet.

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
9.9
EPSS
0.8%
First seen
29 d ago
Status
corroborated

All argoproj vulnerabilities