Most recent entries from all

bdu:2025-14350

2026-10-02T14:29:19.989268+00:00

bdu:2025-14350

Withdrawn: CLEANSTART-2026-AC12204 — go-git is a highly extensible git implementation library written in pure Go

2026-10-02T14:29:19.989320+00:00

Withdrawn by the publisher.

Affected: CleanStart: argo-cd-fips

Multiple security vulnerabilities affect the argo-cd-fips package. go-git is a highly extensible git implementation library written in pure Go. See references for individual vulnerability details.

EUVD-2026-252074

2026-10-02T14:29:19.989364+00:00

EUVD-2026-252074

fkie_cve-2025-55190

2026-10-02T14:29:19.989405+00:00

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.

GHSA-786q-9hcg-v9ff — Argo CD's Project API Token Exposes Repository Credentials

2026-10-02T14:29:19.989456+00:00

Affected: Go: github.com/argoproj/argo-cd/v2, Go: github.com/argoproj/argo-cd/v3

### 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/detaile…

openSUSE-SU-2025:15538-1 — govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media

2026-10-02T14:29:19.989526+00:00

govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media

RHSA-2025:15387 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update

2026-10-02T14:29:19.989561+00:00

github.com/argoproj/argo-cd: Project API Token Exposes Repository Credentials

WID-SEC-W-2025-1978 — Red Hat OpenShift GitOps (Argo CD): Schwachstelle ermöglicht Offenlegung von Informationen

2026-10-02T14:29:19.989585+00:00

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Red Hat OpenShift GitOps (Argo CD) ausnutzen, um Informationen offenzulegen.