External risk intelligence

Argo CD API Tokens Expose Repository Credentials

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2025-55190

Argo CD is a continuous delivery tool commonly deployed as a web-based management interface or API service. Because it functions as a central hub for Kubernetes cluster deployments, these interfaces are frequently exposed to internal networks or via ingress controllers to the internet to facilitate GitOps workflows, making the application API surface commonly reachable in many deployment environments.

Information Disclosure

Argoproj Argo Cd

2.2.0 to before 2.13.92.14.0 to before 2.14.163.0.0 to before 3.0.143.1.0 to before 3.1.2

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

A critical vulnerability exists in Argo CD, a tool used for managing Kubernetes deployments via GitOps. Specifically, certain API tokens could inadvertently expose sensitive repository credentials, even without explicit permissions. This issue impacts how access controls function within Argo CD, potentially leading to unauthorized disclosure of sensitive information.

Sensitive credentials may be exposed via Argo CD.
Leadership should recall Argo CD's role in deployments.
Confirm relevance and assess exposure to Argo CD.

Attack Path

How an attacker could exploit the issue

An attacker with network access and a low-privilege API token could exploit this vulnerability by interacting with Argo CD's project details API. This allows them to retrieve sensitive repository credentials, even if their token doesn't have explicit permission to access secrets, potentially leading to further compromise of the system.

Entry condition: Network access and API token.
Trigger point: Project details API endpoint.
Resulting risk: Sensitive credential exposure.

Live Threat

Current exploitation, exposure, and threat context

API tokens with project-level permissions in Argo CD could expose sensitive repository credentials, such as usernames and passwords, through the project details API endpoint, even when the token lacks explicit secrets access. This exposure can occur when the token has project get permissions, including certain global roles.

Repository credentials could be accessed.
Tokens with project get permissions can retrieve data.
Exposure of sensitive credentials.

Operational Fix

Recommended remediation, mitigation, and detection steps

Argo CD's GitOps functionality and exposure via APIs and web interfaces suggest that platform, infrastructure, or security teams are likely responsible for managing this tool. The initial step is to identify all Argo CD instances, confirm their reachability and criticality, and then locate the accountable owner to plan remediation.

Platform and infrastructure teams own resolution.
Verify Argo CD instances and their network exposure.
Plan remediation based on asset criticality and risk.

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 does it handle sensitive credentials?

Argo CD is a GitOps continuous delivery tool that automates Kubernetes application deployments. It maintains connection strings and authentication details for external version control repositories to pull code and manifests. These credentials are stored by the platform so it can automatically synchronize application states between your Git repositories and your Kubernetes clusters.

How does CVE-2025-55190 allow unauthorized data access?

This vulnerability is classified as CWE-200, or exposure of sensitive information. It occurs because the project details API endpoint fails to properly validate permissions. Instead of restricting access, it incorrectly reveals repository credentials—like usernames and passwords—to any API token that holds basic project 'get' permissions, even if that token is restricted from viewing secrets.

Do I need secret-management permissions for this bug to trigger?

No. The vulnerability does not require high-level secrets access. It triggers whenever a user or automated process with standard project-level read permissions queries the project details API. It is not limited to specific secret-management roles, as even broad global permissions that include 'projects, get' are sufficient to retrieve the sensitive repository data.

Is my instance at risk according to Halo Surface Signal?

Halo Surface Signal notes that Argo CD acts as a central hub for Kubernetes and is often reachable across internal networks or via internet-facing ingress controllers to support GitOps workflows. If your instance is accessible through these network paths, it increases the likelihood that a compromised or low-privilege API token could be used to reach the affected API endpoint.

What is the best way to address this Argo CD security issue?

Your first step is to inventory all running Argo CD instances to determine which versions are in use, as those listed in the advisory are affected. Once identified, coordinate with your platform or infrastructure teams to schedule an update to the patched versions provided by the vendor, which remove the unintended credential exposure in the API.

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.