argoproj · Argo CD · published 2026-10-20

CVE-2026-113672Argo CD: A Jsonnet import can read files from the repo-server

Routine No exploitation evidence; EPSS 0.8%.

CVE-2026-113672 is not known to be exploited in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 58% of all CVEs. This Argo CD vulnerability: CVSS 9.9 (v3.1), a successful attack gives total control of the component. Fixed upstream in Argo CD 3.5.4, 3.4.10, 3.3.15. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Argo CD 3.5.4, 3.4.10, 3.3.15.

Patch events

  1. This monthSecurity release

    OrchestrationArgo CD

    Argo CD security releases: 3.5.4, 3.4.10, 3.3.15

    Upgrade to 3.5.43.4.103.3.15

    Why: CVE-2026-55797: EPSS 2.2% with high severity (CVSS 8.8).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.8% (59th pct)FIRST EPSS v2026.06.15
CVSS base score9.9 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →