cve.bz

CVE-2026-113672 argoproj argo-cd: Path traversal

9.9 criticalEPSS 0.8%

Critical (9.9) in argoproj argo-cd. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-113672 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113672?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113672?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113672 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
argoproj argo-cd>= 0.9.0, < 3.3.1
argoproj argo-cd>= 3.4.0-rc1, < 3.4.10
argoproj argo-cd>= 3.5.0-rc1, < 3.5.4
argoproj argo-cd>= 3.6.0-rc1, < 3.6.0-rc2

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because authenticated remote users with application read access or repository write privileges can extract sensitive repo-server filesystem contents—such as mounted credentials and service account tokens—or exhaust host memory. In typical deployments where Jsonnet rendering is enabled, an attacker can supply malicious imports via Git commits or manifests uploaded during diff operations. However, exploitation is bounded because it requires authenticated interaction with existing applications, limiting the overall blast radius.

Red Hat's mitigation

This flaw can be mitigated by disabling Jsonnet processing in the repo-server. Set the following key in the `argocd-cm` ConfigMap in the namespace where Argo CD / Red Hat OpenShift GitOps is installed:

jsonnet.enable: "false"

With this setting Argo CD skips all `.jsonnet` files, closing both attack vectors (a `.jsonnet` file committed to a Git repository and one uploaded via `POST /api/v1/applications/manifestsWithFiles`). YAML and JSON manifests in a directory Application continue to be applied.

Note: this workaround is not transparent to Jsonnet users. Applications that rely on Jsonnet will stop rendering those files — the manifests are omitted rather than rejected, so a directory Application containing only Jsonnet will sync without those manifests. Review affected Applications before applying.

ProductPackageStateAdvisory
Red Hat Openshift Data Foundation 4odf4/odf-multicluster-rhel9-operatorNot affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-agent-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-image-updater-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/gitops-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/gitops-rhel9-operatorNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-113672.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON