External risk intelligence

Argo CD Kustomize Command Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-113708

Argo CD is a continuous delivery tool commonly deployed as an internet-facing web application or API service to manage Kubernetes deployments. While this specific vulnerability requires authenticated access to the application's API endpoints, the product itself is frequently exposed to the internet or accessible via management surfaces to facilitate GitOps workflows and remote cluster administration.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in Argo CD, a tool used for managing Kubernetes deployments. The issue could allow an attacker to execute commands within the Argo CD environment by manipulating Git repository references, potentially impacting sensitive data and operational integrity.

Issue allows command execution via Git references.
Matters for securing deployment pipelines and sensitive data.
Confirm relevance and assess exposure to GitOps tools.

Attack Path

How an attacker could exploit the issue

An attacker could compromise Argo CD by crafting a malicious Kustomization file or uploading files through an API endpoint. This crafted input, when processed by a vulnerable Kustomize component within the argocd-repo-server, can trick the Git fetch command into executing arbitrary code. The execution occurs within the repo-server's environment, allowing potential access to sensitive credentials and other data.

Attacker starts with Git repository access.
Vulnerable Kustomize processes malicious input.
Risk of code execution and credential theft.

Live Threat

Current exploitation, exposure, and threat context

When Kustomize uses local transport with a specially crafted URL, an attacker could execute commands within the Argo CD repo-server. This could allow an attacker to read repository credentials and other process-accessible data. The command execution does not leave the pod, but the output can be returned via manifest-generation errors.

Repository credentials could be exposed.
Commands executed via malicious Kustomization files.
Sensitive data exposure and unauthorized access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Argo CD GitOps tool, when using Kustomize, presents a critical risk if not properly secured. Responsibility for addressing this likely falls to the platform or infrastructure teams managing Argo CD, in coordination with security teams. The immediate priority is to locate all instances of the affected Argo CD versions, assess their exposure and business criticality, and identify the accountable application or system owner. Remediation planning should then be based on this risk assessment, potentially involving vendor coordination or temporary risk reduction measures.

Platform/Infrastructure and Security teams own this.
Verify Argo CD instances and their reachability.
Plan remediation based on risk and criticality.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Argo CD and why is it used?

Argo CD is a GitOps delivery tool designed for Kubernetes environments. It automates the deployment of applications by continuously monitoring Git repositories and syncing their contents to a cluster. It relies on components like Kustomize to render configuration files, acting as a bridge between your version control system and live cluster state.

How does CVE-2026-113708 work as a vulnerability?

This is an example of Improper Neutralization of Argument-related Special Elements, or CWE-88. The vulnerability occurs because the Kustomize component passes user-controlled strings directly to a Git command without separators. An attacker can use a leading hyphen to masquerade input as a command-line flag, tricking the system into executing unauthorized instructions within the repo-server environment.

What triggers this command execution?

The vulnerability is triggered when Kustomize processes a URL using local file transport, such as file://. If the input includes a specially crafted git ref or version string, the system parses it as a command argument. Crucially, this does not occur with standard https:// remote connections, as Git does not treat the supplied input as an executable command in that specific transport context.

Do I need to worry if my instance is internal?

Yes, you should assess your risk regardless of placement. While Halo Surface Signal notes that Argo CD is often deployed as an internet-facing service, this vulnerability is reachable through API endpoints that allow manifest uploads or repository references. Since an attacker only needs basic access to perform these actions, even internal instances can be compromised if an attacker gains entry to your network.

How should I respond to this threat?

Start by identifying all Argo CD instances running versions 2.7.0 through 3.6.0-rc2. The primary solution is to upgrade to the patched versions: 3.3.15, 3.4.10, 3.5.4, or 3.6.0-rc2. Simply updating the Kustomize tool is insufficient, as the flaw lies in how Argo CD handles the command-line arguments, making the direct application update the required remediation.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.