Most recent entries from all

bdu:2023-05691

2026-10-17T05:25:12.609428+00:00

bdu:2023-05691

EUVD-2026-221784

2026-10-17T05:25:12.609466+00:00

EUVD-2026-221784

fkie_cve-2023-22482

2026-10-17T05:25:12.609480+00:00

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions of Argo CD starting with v1.8.2 and prior to 2.3.13, 2.4.19, 2.5.6, and 2.6.0-rc-3 are vulnerable to an improper authorization bug causing the API to accept certain invalid tokens. OIDC providers include an `aud` (audience) claim in signed tokens. The value of that claim specifies the intended audience(s) of the token (i.e. the service or services which are meant to accept the token). Argo CD _does_ validate that the token was signed by Argo CD's configured OIDC provider. But Argo CD _does not_ validate the audience claim, so it will accept tokens that are not intended for Argo CD. If Argo CD's configured OIDC provider also serves other audiences (for example, a file storage service), then Argo CD will accept a token intended for one of those other audiences. Argo CD will grant the user privileges based on the token's `groups` claim, even though those groups were not intended to be used by Argo CD. This bug also increases the impact of a stolen token. If an attacker steals a valid token for a different audience, they can use it to access Argo CD. A patch for this vulnerability has been released in versions 2.6.0-rc3, 2.5.6, 2.4.19, and 2.3.13. There are no workarounds.

GHSA-q9hr-j4rf-8fjc — JWT audience claim is not verified

2026-10-17T05:25:12.609518+00:00

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

### Impact

All versions of Argo CD starting with v1.8.2 are vulnerable to an improper authorization bug causing the API to accept certain invalid tokens.

OIDC providers include an `aud` (audience) claim in signed tokens. The value of that claim specifies the intended audience(s) of the token (i.e. the service or services which are meant to accept the token). Argo CD _does_ validate that the token was signed by Argo CD's configured OIDC provider. But Argo CD _does not_ validate the audience claim, so it will accept tokens that are not intended for Argo CD.

If Argo CD's configured OIDC provider also serves other audiences (for example, a file storage service), then Argo CD will accept a token intended for one of those other audiences. Argo CD will grant the user privileges based on the token's `groups` claim, even though those groups were not intended to be used by Argo CD.

This bug also increases the blast radius of a stolen token. If an attacker steals a valid token for a different audience, they can use it to access Argo CD.

### Patches

A patch for this vulnerability has been released in the following Argo CD versions:

* v2.6.0-rc5 * v2.5.8 * v2.4.20 * v2.3.14

The patch introduces a new `allowedAudiences` to the OIDC config block. By default, the client ID is the only allowed audience. Users who _want_ Argo CD to accept tokens intended for a different audience may use `allowedAudiences` to specify those audiences.

```yaml apiVersion: v1 kind: ConfigMap metadata:…

gsd-2023-22482

2026-10-17T05:25:12.609574+00:00

gsd-2023-22482

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

2026-10-17T05:25:12.609588+00:00

ArgoCD: JWT audience claim is not verified

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

2026-10-17T05:25:12.609605+00:00

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