CVSS 3.1
9.9 criticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCritical (9.9) in argoproj argo-cd. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| 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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Openshift Data Foundation 4 | odf4/odf-multicluster-rhel9-operator | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-agent-rhel9 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-image-updater-rhel9 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-rhel9 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/gitops-rhel9 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/gitops-rhel9-operator | Not 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.