Most recent entries from all

bdu:2023-00641

2026-10-17T02:48:13.656258+00:00

bdu:2023-00641

EUVD-2026-221645

2026-10-17T02:48:13.656290+00:00

EUVD-2026-221645

fkie_cve-2023-22736

2026-10-17T02:48:13.656304+00:00

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions starting with 2.5.0-rc1 and above, prior to 2.5.8, and version 2.6.0-rc4, are vulnerable to an authorization bypass bug which allows a malicious Argo CD user to deploy Applications outside the configured allowed namespaces. Reconciled Application namespaces are specified as a comma-delimited list of glob patterns. When sharding is enabled on the Application controller, it does not enforce that list of patterns when reconciling Applications. For example, if Application namespaces are configured to be argocd-*, the Application controller may reconcile an Application installed in a namespace called other, even though it does not start with argocd-. Reconciliation of the out-of-bounds Application is only triggered when the Application is updated, so the attacker must be able to cause an update operation on the Application resource. This bug only applies to users who have explicitly enabled the "apps-in-any-namespace" feature by setting `application.namespaces` in the argocd-cmd-params-cm ConfigMap or otherwise setting the `--application-namespaces` flags on the Application controller and API server components. The apps-in-any-namespace feature is in beta as of this Security Advisory's publish date. The bug is also limited to Argo CD instances where sharding is enabled by increasing the `replicas` count for the Application controller. Finally, the AppProjects' `sourceNamespaces` field acts as a sec…

GHSA-6p4m-hw2h-6gmw — Controller reconciles apps outside configured namespaces when sharding is enabled

2026-10-17T02:48:13.656355+00:00

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

### Impact

All Argo CD versions starting with 2.5.0-rc1 are vulnerable to an authorization bypass bug which allows a malicious Argo CD user to deploy Applications outside the configured allowed namespaces.

#### Description of exploit

Reconciled Application namespaces are specified as a comma-delimited list of glob patterns. When sharding is enabled on the Application controller, it does not enforce that list of patterns when reconciling Applications. For example, if Application namespaces are configured to be `argocd-*`, the Application controller may reconcile an Application installed in a namespace called `other`, even though it does not start with `argocd-`.

Reconciliation of the out-of-bounds Application is only triggered when the Application is updated, so the attacker must be able to cause an update operation on the Application resource.

#### Limitations

This bug only applies to users who have explicitly enabled the "apps-in-any-namespace" feature by setting `application.namespaces` in the argocd-cmd-params-cm ConfigMap or otherwise setting the `--application-namespaces` flags on the Application controller and API server components. The apps-in-any-namespace feature is in beta as of this Security Advisory's publish date.

The bug is also limited to Argo CD instances where sharding is enabled by increasing the `replicas` count for the Application controller.

Finally, the AppProjects' `sourceNamespaces` field acts as a secondary check against this exploit. To cau…

gsd-2023-22736

2026-10-17T02:48:13.656403+00:00

gsd-2023-22736

RHSA-2023:0467 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update

2026-10-17T02:48:13.656416+00:00

ArgoCD: JWT audience claim is not verified argocd: Controller reconciles apps outside configured namespaces when sharding is enabled

WID-SEC-W-2023-0201 — Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

2026-10-17T02:48:13.656435+00:00

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Sicherheitsvorkehrungen zu umgehen.