Skip to main content
VulnerabilityPublished

CVE-2025-55190: argoproj argo-cd · Information Exposure

Affects argoproj argo-cdSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical · fixed in 2.13.9 : patch argoproj argo-cd as a priority.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
5.6% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.13.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

AI-suggested

European organizations should immediately audit their Argo CD deployments to identify affected versions and upgrade to patched releases (2.13.9, 2.14.16, 3.0.14, or 3.1.2). Beyond patching, organizations should enforce the principle of least privilege by reviewing and restricting API token permissions, ensuring tokens do not have unnecessary project get or global permissions. Implement strong authentication and authorization controls around Argo CD API access, including the use of short-lived tokens and regular token rotation. Monitor API access logs for anomalous requests to the project details endpoint that could indicate exploitation attempts. Employ network segmentation and firewall rules to limit access to Argo CD APIs only to trusted management networks. Integrate secrets management solutions external to Argo CD to reduce reliance on embedded repository credentials. Conduct regular security assessments and penetration tests focused on GitOps pipelines and Kubernetes deployment tools. Finally, educate DevOps teams about the risks of over-permissioned tokens and the importance of timely patching.

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.

References

Community reviews

Loading reviews…