# Argo CD will blindly trust JWT claims if anonymous access is enabled in github.com/argoproj/argo-cd

Advisory record · `GHSA-r642-gv9p-2wjj`

- **Identifiers:** `GHSA-r642-gv9p-2wjj` · `CVE-2022-29165` · `GO-2022-0455`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-290](https://cwe.mitre.org/data/definitions/290.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 21 Aug 2024
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

[Published by the maintainers](https://github.com/argoproj/argo-cd/security/advisories/GHSA-r642-gv9p-2wjj) · not yet reviewed by GitHub. The argoproj/argo-cd maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the argoproj/argo-cd maintainers at 21 Aug 2024, 15:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/argoproj/argo-cd` (Go): affected `all versions`; no fixed version yet
- `github.com/argoproj/argo-cd/v2` (Go): affected `<2.1.15 || >=2.2.0, <2.2.9 || >=2.3.0, <2.3.4`; fixed in `2.1.15`, `2.2.9`, `2.3.4`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 82nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 18 May 2022, 13:08 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/argoproj/argo-cd/security/advisories/GHSA-r642-gv9p-2wjj)

## Sources

- [GitHub Advisory Database: GHSA-r642-gv9p-2wjj](https://github.com/advisories/GHSA-r642-gv9p-2wjj)
- [OSV: GHSA-r642-gv9p-2wjj](https://osv.dev/vulnerability/GHSA-r642-gv9p-2wjj)
- <https://github.com/argoproj/argo-cd/security/advisories/GHSA-r642-gv9p-2wjj>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-29165>
- <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>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r642-gv9p-2wjj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r642-gv9p-2wjj/>. Everything for agents: <https://agentprime.io/llms.txt>.
