Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions of Argo CD starting with…

CVSS 3.1 · [email protected] · Secondary 9.0 CRITICALCVSS 3.1 · [email protected] · Primary 8.8 HIGHCheck source for fixed versionsKEV status unknown

Historical advisory recorded 24 Oct 2026 21:17:28 UTC. Read the latest advisory.

nvd · CVE-2023-22482

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

nvd · CVE-2023-22482

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-863

Original publisher date fields

published: 2023-01-26T21:18:12.213

lastModified: 2026-06-17T05:35:33.353

5 source CPE criteria · context only
  • cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*
  • cpe:2.3:a:argoproj:argo_cd:2.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:argoproj:argo_cd:2.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:argoproj:argo_cd:2.6.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:argoproj:argo_cd:2.6.0:rc4:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 09:03 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current