CVE-2025-55190: Github.com/argoproj/argo cd/v2 Argo CD's Project API Token Vulnerability

CRITICAL
Advisory Identifier: GHSA-786q-9hcg-v9ff
CVSS 9.9
CWE-200
Published
Advisory Summary

CVE-2025-55190 is a CRITICAL (CVSS 9.9) argo cd's project api token vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/argoproj/argo cd/v2 libraries in the Go ecosystem. The issue involves argo cd's project api token exposes repository credentials. Remediation is available by upgrading affected packages to version 2.13.9, 2.14.16, 3.0.14, 3.1.2.

CVE-2025-55190 at a Glance

CVE Identifier CVE-2025-55190
GHSA Identifier GHSA-786q-9hcg-v9ff
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/argoproj/argo cd/v2
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-55190

To remediate this vulnerability, upgrade all affected Github.com/argoproj/argo cd/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/argoproj/argo-cd/v2 fixed: 2.13.9
Upgrade github.com/argoproj/argo-cd/v2 to 2.13.9
github.com/argoproj/argo-cd/v2 fixed: 2.14.16
Upgrade github.com/argoproj/argo-cd/v2 to 2.14.16
github.com/argoproj/argo-cd/v3 fixed: 3.0.14
Upgrade github.com/argoproj/argo-cd/v3 to 3.0.14
github.com/argoproj/argo-cd/v3 fixed: 3.1.2
Upgrade github.com/argoproj/argo-cd/v3 to 3.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/argoproj/argo-cd/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-55190, inspect your project dependencies for Github.com/argoproj/argo cd/v2:

inspect dependencies for github.com/argoproj/argo-cd/v2

Analyze the terminal output to locate any version of Github.com/argoproj/argo cd/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.13.9), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Github.com/argoproj/argo cd/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Argo CD 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. Component: `Project API (/api/v1/projects/{project}/detailed)` ## Vulnerability Details ### Expected Behavior API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets. ### Actual Behavior API tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint. **Note**: 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` ### Steps to Reproduce 1. Create an API token with the following project-level permissions: ``` p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow p, proj:myProject:project-automation-role, applications, get, myProject/*, allow ``` 2. Call the project details API: ``` bashcurl -sH "Authorization: Bearer $ARGOCD_API_TOKEN" \ "https://argocd.example.com/api/v1/projects/myProject/detailed" ``` 3. Observe that the response includes sensitive repository credentials: ``` { "repositories": [ { "username": "<REDACTED>", "password": "<REDACTED>", "type": "helm", "name": "test-helm-repo", "project": "myProject" } ] } ``` ## Patches * v3.1.2 * v3.0.14 * v2.14.16 * v2.13.9 Credits to @ashishgoyal111 for helping identify this issue.

CVE-2025-55190 Affected Github.com/argoproj/argo cd/v2 Versions

4 component(s)
Fixed Versions:
2.13.92.14.163.0.143.1.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/argoproj/argo-cd/v2
Go
≥ 2.13.0
< 2.13.9
2.13.9
github.com/argoproj/argo-cd/v2
Go
≥ 2.14.0
< 2.14.16
2.14.16
github.com/argoproj/argo-cd/v3
Go
< 3.0.14
3.0.14
github.com/argoproj/argo-cd/v3
Go
≥ 3.1.0-rc1
< 3.1.2
3.1.2

References

Frequently Asked Questions

What is CVE-2025-55190?
CVE-2025-55190 is a security vulnerability in Github.com/argoproj/argo cd/v2 involving Argo CD's Project API Token Exposes Repository Credentials under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/argoproj/argo cd/v2 versions are affected?
Affected versions include releases prior to 2.13.9, 2.14.16, 3.0.14, 3.1.2 across affected packages: github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3.
What version fixes CVE-2025-55190?
Upgrading to 2.13.9, 2.14.16, 3.0.14, 3.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/argoproj/argo-cd/v2 affected?
Yes, github.com/argoproj/argo-cd/v2 is affected in releases prior to 2.13.9, 2.14.16. Upgrade your dependency to 2.13.9, 2.14.16 or later.
Is github.com/argoproj/argo-cd/v3 affected?
Yes, github.com/argoproj/argo-cd/v3 is affected in releases prior to 3.0.14, 3.1.2. Upgrade your dependency to 3.0.14, 3.1.2 or later.
What is the CVSS score of CVE-2025-55190?
CVE-2025-55190 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2025-55190?
CVE-2025-55190 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for CVE-2025-55190?
Run the dependency tree command: 'inspect dependencies for github.com/argoproj/argo-cd/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-786q-9hcg-v9ff",
  "modified" : "2025-09-05T16:09:59Z",
  "published" : "2025-09-04T19:49:56Z",
  "aliases" : [ "CVE-2025-55190" ],
  "summary" : "Argo CD's Project API Token Exposes Repository Credentials",
  "details" : "### Summary\nArgo CD 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.\n\nComponent: `Project API (/api/v1/projects/{project}/detailed)`\n\n\n## Vulnerability Details\n### Expected Behavior\nAPI tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets.\n### Actual Behavior\nAPI tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.\n\n**Note**: 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`\n\n### Steps to Reproduce\n\n1. Create an API token with the following project-level permissions:\n  ```\n  p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow\n  p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow\n  p, proj:myProject:project-automation-role, applications, get, myProject/*, allow\n  ```\n\n2. Call the project details API:\n  ```\n  bashcurl -sH \"Authorization: Bearer $ARGOCD_API_TOKEN\" \\\n    \"https://argocd.example.com/api/v1/projects/myProject/detailed\"\n  \n  ```\n3. Observe that the response includes sensitive repository credentials:\n  ```\n  {\n    \"repositories\": [\n      {\n        \"username\": \"<REDACTED>\",\n        \"password\": \"<REDACTED>\",\n        \"type\": \"helm\",\n        \"name\": \"test-helm-repo\",\n        \"project\": \"myProject\"\n      }\n    ]\n  }\n  ```\n\n## Patches\n\n* v3.1.2\n* v3.0.14\n* v2.14.16\n* v2.13.9\n\n\nCredits to @ashishgoyal111 for helping identify this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.13.0"
      }, {
        "fixed" : "2.13.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.14.0"
      }, {
        "fixed" : "2.14.16"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.1.0-rc1"
      }, {
        "fixed" : "3.1.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/security/advisories/GHSA-786q-9hcg-v9ff"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-55190"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/e8f86101f5378662ae6151ce5c3a76e9141900e8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/argoproj/argo-cd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-04T19:49:56Z",
    "nvd_published_at" : "2025-09-04T23:15:32Z"
  }
}