dbcve.org
Argo CdApplication · Argoproj

CVE-2025-55190

CRITICAL · 9.9 CVSS v3.1 Published 2025-09-04
Fix available
A fix is available. Upgrade to 2.13.9 / 2.14.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Argo CD versions 2.13.0-2.13.8, 2.14.0-2.14.15, 3.0.0-3.0.12, and 3.1.0-rc1-3.1.1 contain an improper authorization vulnerability in the project details API endpoint. Tokens with only project-level 'get' permissions (or global permissions like `p, role/user, projects, get, *, allow`) can retrieve sensitive repository credentials including usernames and passwords that should be restricted from their access level.

MitigationUpgrade Argo CD to version 2.13.9, 2.14.16, 3.0.14, or 3.1.2. Review token permissions and audit logs for unauthorized credential access; rotate any exposed credentials immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Argo CdApplication
Affected:>= 2.2.0, < 2.13.9>= 2.14.0, < 2.14.16>= 3.0.0, < 3.0.14>= 3.1.0, < 3.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Argo CD version
    Run 'argocd version' CLI or check the container/manifest version deployed in your cluster. For Kubernetes deployments, inspect the Argo CD namespace (usually argocd) for the deployed image tag or version configmap.
    Affected if The installed version falls within 2.13.0-2.13.8, 2.14.0-2.14.15, 3.0.0-3.0.12, or 3.1.0-rc1-3.1.1 (or equivalently >=2.2.0 <2.13.9, >=2.14.0 <2.14.16, >=3.0.0 <3.0.14, >=3.1.0 <3.1.2)
  2. Review API tokens with project-level get permissions
    Examine Argo CD project roles and global roles. Look for tokens, service accounts, or roles that have been granted only 'get' permission on projects (such as 'p, <user>, <project>, get, *, allow') or global 'projects, get' permissions without 'update' or 'admin' rights.
    Affected if Tokens exist with only project-level 'get' permissions (or matching the pattern 'p, role/user, projects, get, *, allow') that can access project resources
  3. Test project API endpoint authorization
    Using a token with only project-level 'get' permissions (or the global 'p, role/user, projects, get, *, allow' permission), make a GET request to the project details API endpoint (for example: GET /api/v1/projects/<project-name>) and inspect whether the response includes repository credentials with sensitive fields such as 'password', 'sshPrivateKey', or 'tlsClientCertKey'.
    Affected if The API returns repository credentials (usernames, passwords, keys, or certificates) to a token that only has 'get' permission on the project
  4. Audit access logs for credential retrieval
    Review Argo CD audit logs, specifically look for API calls to project endpoints from accounts with only 'get' permissions that resulted in responses containing repository configuration data.
    Affected if Logs show project 'get' permission requests returning repository credential data

You are affected if your Argo CD version is 2.13.0-2.13.8, 2.14.0-2.14.15, 3.0.0-3.0.12, or 3.1.0-3.1.1 AND you have tokens with only project-level get permissions that can access the project details API endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.13.9 / 2.14.16 / 3.0.14 or later
Fixed in 2.13.92.14.163.0.14
Vendor patch github.com →
Interim mitigation

Upgrade Argo CD to version 2.13.9, 2.14.16, 3.0.14, or 3.1.2. Review token permissions and audit logs for unauthorized credential access; rotate any exposed credentials immediately.

Recommended fix High confidence

Upgrade to 2.13.9, 2.14.16, 3.0.14, or 3.1.2 (minimum fixed versions based on current branch)

  1. 1. Identify current Argo CD version by checking the Argo CD namespace (e.g., kubectl get argocd -n argocd -o jsonpath='{.items[0].status.controllerVersion}' or checking the deployment image tag)
  2. 2. Based on the current version, determine the appropriate upgrade path from the fixed releases: 2.13.9, 2.14.16, 3.0.14, or 3.1.2
  3. 3. For versions 2.2.0 to 2.13.8: upgrade to 2.13.9 or later (recommended 2.14.16 for latest features and security)
  4. 4. For versions 2.14.0 to 2.14.15: upgrade to 2.14.16
  5. 5. For versions 3.0.0 to 3.0.12: upgrade to 3.0.14
  6. 6. For versions 3.1.0 to 3.1.1: upgrade to 3.1.2
  7. 7. Review release notes for the target version to check for any breaking changes or migration requirements
  8. 8. Perform the upgrade using the standard Argo CD upgrade process (e.g., kubectl apply -f for the new manifest, or use the upgrade feature in Argo CD UI/CLI)
Caveat Review version-specific release notes for potential breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Argo Cd Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55190 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data