CVSS 3.1
9.9 criticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCritical (9.9) in argoproj argo cd. EPSS 5.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-cd/v2 2.13.9, 2.14.16.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hgithub.com/argoproj/argo-cd/v2 (Go): fixed in 2.13.9, 2.14.16github.com/argoproj/argo-cd/v3 (Go): fixed in 3.0.14, 3.1.2Explain CVE-2025-55190 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-55190?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-55190?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-55190 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| argoproj:argo_cd | from 2.2.0 before 2.13.9 |
| argoproj:argo_cd | from 2.14.0 before 2.14.16 |
| argoproj:argo_cd | from 3.0.0 before 3.0.14 |
| argoproj:argo_cd | from 3.1.0 before 3.1.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-786q-9hcg-v9ff | Go | github.com/argoproj/argo-cd/v2 | >=2.13.0 <2.13.9 | 2.13.9 |
| GHSA-786q-9hcg-v9ff | Go | github.com/argoproj/argo-cd/v2 | >=2.14.0 <2.14.16 | 2.14.16 |
| GHSA-786q-9hcg-v9ff | Go | github.com/argoproj/argo-cd/v3 | <3.0.14 | 3.0.14 |
| GHSA-786q-9hcg-v9ff | Go | github.com/argoproj/argo-cd/v3 | >=3.1.0-rc1 <3.1.2 | 3.1.2 |
| GO-2025-3934 | Go | github.com/argoproj/argo-cd | all versions | no fix published |
| GO-2025-3934 | Go | github.com/argoproj/argo-cd/v2 | >=2.13.0 <2.13.9 >=2.14.0 <2.14.16 | 2.13.9, 2.14.16 |
| GO-2025-3934 | Go | github.com/argoproj/argo-cd/v3 | <3.0.14 >=3.1.0-rc1 <3.1.2 | 3.0.14, 3.1.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20250918T182144-150000.1.107.1 | SUSE-SU-2025:03289-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20250918T182144-150000.1.107.1 | SUSE-SU-2025:03289-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20250908T141310-1.1 | openSUSE-SU-2025:15538-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Important.
This vulnerability has Important impact as exploitation requires some privileges granted by the system. An attacker would either need the ability to create an API token (via having valid login credentials) or to have stolen an API token from a legitimate user. It does not grant full control over the system, attackers can only tamper with the project(s) associated with an API token.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift GitOps 1.15 | openshift-gitops-1/gitops-operator-bundle:1.15 | Fixed 2025-09-04 | RHSA-2025:15387 |
| Red Hat OpenShift GitOps 1.15 | openshift-gitops-1/gitops-rhel8-operator:1.15 | Fixed 2025-09-04 | RHSA-2025:15387 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/gitops-operator-bundle:1.16 | Fixed 2025-09-04 | RHSA-2025:15388 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/gitops-rhel8-operator:1.16 | Fixed 2025-09-04 | RHSA-2025:15388 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/gitops-operator-bundle:1.17 | Fixed 2025-09-04 | RHSA-2025:15389 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/gitops-rhel8-operator:1.17 | Fixed 2025-09-04 | RHSA-2025:15389 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/gitops-rhel8:1768824960 | Fixed 2026-01-22 | RHSA-2026:1018 |
| Red Hat OpenShift GitOps 1.18 | openshift-gitops-1/gitops-rhel8:1768881034 | Fixed 2026-01-22 | RHSA-2026:1017 |
| Red Hat OpenShift GitOps 1.19 | openshift-gitops-1/gitops-rhel8:1769165422 | Fixed 2026-01-28 | RHSA-2026:1488 |
| Red Hat Developer Hub 1 | rhdh-orchestrator-dev-preview-beta/orchestrator-operator-bundle | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-agent-rhel8 | Affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-extensions-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-rhel8 | Affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-rhel9 | Affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argo-rollouts-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/console-plugin-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/dex-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/must-gather-rhel8 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-55190.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).