https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T13:59:51.791413+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-189059 EUVD-2026-189059 2026-10-16T13:59:51.797400+00:00 EUVD-2026-189059 https://cve.radiocsirt.org/vuln/fkie_cve-2023-40029 fkie_cve-2023-40029 2026-10-16T13:59:51.797443+00:00

Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored in`kubectl.kubernetes.io/last-applied-configuration` annotation. pull request #7139 introduced the ability to manage cluster labels and annotations. Since clusters are stored as secrets it also exposes the `kubectl.kubernetes.io/last-applied-configuration` annotation which includes full secret body. In order to view the cluster annotations via the Argo CD API, the user must have `clusters, get` RBAC access. **Note:** In many cases, cluster secrets do not contain any actually-secret information. But sometimes, as in bearer-token auth, the contents might be very sensitive. The bug has been patched in versions 2.8.3, 2.7.14, and 2.6.15. Users are advised to upgrade. Users unable to upgrade should update/deploy cluster secret with `server-side-apply` flag which does not use or rely on `kubectl.kubernetes.io/last-applied-configuration` annotation. Note: annotation for existing secrets will require manual removal.

 https://cve.radiocsirt.org/vuln/ghsa-fwr2-64vr-xv9m GHSA-fwr2-64vr-xv9m — Argo CD cluster secret might leak in cluster details page 2026-10-16T13:59:51.797497+00:00

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

### Impact

Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored in`kubectl.kubernetes.io/last-applied-configuration` annotation.

https://github.com/argoproj/argo-cd/pull/7139 introduced the ability to manage cluster labels and annotations. Since clusters are stored as secrets it also exposes the `kubectl.kubernetes.io/last-applied-configuration` annotation which includes full secret body. In order to view the cluster annotations via the Argo CD API, the user must have `clusters, get` RBAC access.

**Note:** In many cases, cluster secrets do not contain any actually-secret information. But sometimes, as in bearer-token auth, the contents might be very sensitive.

### Patches

The bug has been patched in the following versions:

* 2.8.3 * 2.7.14 * 2.6.15

### Workarounds

Update/Deploy cluster secret with `server-side-apply` flag which does not use or rely on `kubectl.kubernetes.io/last-applied-configuration` annotation. Note: annotation for existing secrets will require manual removal.

### For more information

* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

 https://cve.radiocsirt.org/vuln/gsd-2023-40029 gsd-2023-40029 2026-10-16T13:59:51.797598+00:00 gsd-2023-40029 https://cve.radiocsirt.org/vuln/rhsa-2023:5029 RHSA-2023:5029 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update 2026-10-16T13:59:51.797620+00:00

ArgoCD: secrets can be leak through kubectl.kubernetes.io/last-applied-configuration ArgoCD: Denial of Service to Argo CD repo-server

 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2296 WID-SEC-W-2023-2296 — Red Hat OpenShift: Mehrere Schwachstellen 2026-10-16T13:59:51.797650+00:00

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.