Homepage

Information Exposure Affecting argocd-fips-3.1 package, versions <3.1.3-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.05% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-ARGOCDFIPS31-13332431
  • published6 Oct 2025
  • disclosed4 Sept 2025
Report a new vulnerability Found a mistake?

Introduced: 4 Sep 2025

CVE-2025-55190  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argocd-fips-3.1 to version 3.1.3-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argocd-fips-3.1 package and not the argocd-fips-3.1 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.