External risk intelligence

Argo CD Repo-Server File Access Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-113672

Argo CD is a continuous delivery tool commonly deployed as an internet-accessible web application and API service to manage Kubernetes deployments. While the vulnerability requires existing lower-level permissions within the platform, the service itself is frequently exposed to network access to facilitate CI/CD workflows, making the interface a common target in standard GitOps deployment patterns.

Path Traversal

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 vulnerability in Argo CD could allow unauthorized access to sensitive files, such as service account tokens or private keys, by manipulating configuration files. It impacts the tool's ability to securely manage Kubernetes environments through GitOps, potentially exposing critical credentials and system information.

Configuration files can expose sensitive system data.
It affects GitOps delivery tools for Kubernetes.
Confirm relevance and review exposure of Argo CD deployments.

Attack Path

How an attacker could exploit the issue

An attacker could begin by committing a specially crafted `.jsonnet` file to a Git repository that Argo CD monitors. Alternatively, an attacker with existing permissions to view an application's manifests could upload this file directly. When Argo CD's repo-server processes this file, the vulnerability allows it to read any file accessible by the server, potentially exposing sensitive data such as service account tokens or private keys, or causing a denial-of-service by exhausting memory. The sensitive data can then be exfiltrated by placing it in a ConfigMap.

Requires existing application read permissions.
Triggered by processing a malicious `.jsonnet` file.
Risk includes sensitive data exposure and denial-of-service.

Live Threat

Current exploitation, exposure, and threat context

When Argo CD's repo-server processes `.jsonnet` files, it can be tricked into reading any file accessible to the service account. This could expose sensitive information like service account tokens or private keys. An attacker could also cause the service to consume excessive memory by importing from specific devices.

Sensitive files readable by repo-server.
Via malicious .jsonnet file import.
Information disclosure and service disruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for Argo CD, likely platform or Kubernetes infrastructure teams, should begin by identifying all deployments of the affected tool. Next, confirm reachability and business criticality for each instance to prioritize remediation efforts and engage the accountable owner.

Identify Argo CD ownership and scope.
Verify accessible instances and business impact.
Plan vendor coordination and targeted updates.

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 continuous delivery tool that automates the deployment of applications into Kubernetes clusters. It uses a declarative approach, meaning it continuously monitors Git repositories for configuration changes and automatically synchronizes the cluster state to match what is defined in those repositories. This streamlines infrastructure management by treating application manifests as the single source of truth.

What is the vulnerability in CVE-2026-113672?

This vulnerability is classified as CWE-22, or Path Traversal. In Argo CD, the repo-server component processes .jsonnet files but fails to properly restrict file imports to the repository root. This weakness allows the server to be manipulated into reading arbitrary files from the local filesystem—such as private keys or system tokens—that it should not have access to, rather than just the configuration files it is intended to process.

How does an attacker trigger this file access?

An attacker triggers the bug by providing a crafted .jsonnet file that uses path traversal techniques to reference files outside the permitted directory. This can be done by committing the file to a Git repository monitored by Argo CD or by uploading it through specific API endpoints. It is important to note that the vulnerability is not triggered by standard, legitimate configuration files; it requires the inclusion of specific import instructions designed to escape the expected file scope.

Do I need to worry if my Argo CD is internal?

You should still prioritize this vulnerability regardless of network placement. According to Halo Surface Signal, Argo CD is frequently deployed as an internet-accessible service to support CI/CD workflows, which increases the likelihood of exposure. Even for internal instances, the risk remains significant because the exploit only requires existing, lower-level application read permissions, which may already be available to a broad range of internal users.

How do I start addressing this issue?

Begin by identifying all Argo CD instances running in your environment to understand your total scope. Once you have an inventory, verify which versions are currently deployed to determine if they fall within the affected range. Prioritize updating those instances to the patched versions provided by the vendor, which contain the necessary fixes to properly restrict file imports within the repo-server.

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.