CVE-2023-22482

JWT audience claim is not verified

HIGH
8.8
CVSS Score
Published: January 25, 2023 at 06:25 PM UTC
Updated: June 17, 2026 at 05:35 AM UTC
1 product affected across 1 vendorArgo CD

Using argo-cd by argoproj?

Get instant alerts when new vulnerabilities affect argo-cd - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.9%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.3.13v < 2.4.19v < 2.5.6v < 2.6.0-rc31.8.2 ≤ v < 2.3.142.4.0 ≤ v < 2.4.202.5.0 ≤ v < 2.5.82.6.0 rc12.6.0 rc22.6.0 rc32.6.0 rc4
Affected range stops below 2.3.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.5.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.5.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.6.0-rc3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card