# CVE-2022-29164: Privilege Escalation in argo-workflows

> An insider can exploit stored XSS in Argo Workflows artifacts to execute scripts as a victim, reading or modifying their workflows.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-argo-workflows-2022-29164, GHSA-cmv8-6362-r5w9, MINI-99q2-9328-2f2h, MINI-wv79-5jmc-xmgg

## What is CVE-2022-29164?

CVE-2022-29164 is a high-severity cross-site scripting vulnerability in argoproj argo-workflows, published on 5 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. In affected versions an attacker can create a workflow which produces a HTML artifact containing an HTML file that contains a script which uses XHR calls to interact with the Argo Server API. The attacker emails the deep-link to the artifact to their victim. The victim opens the link, the script starts running. As the script has access to the Argo Server API (as the victim), so may read information about the victim’s workflows, or create and delete workflows. Note the attacker must be an insider: they must have access to the same cluster as the victim and must already be able to run their own workflows. The attacker must have an understanding of the victim’s system. We have seen no evidence of this in the wild. We urge all users to upgrade to the fixed versions.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2022-29164?

5 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v3 and argo-workflows. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-workflows/v3` | Go | From 2.6.0 | 3.2.11 |
| `github.com/argoproj/argo-workflows/v3` | Go | From 2.6.0 | 3.2.11 |
| `github.com/argoproj/argo-workflows/v3` | Go | From 3.3.0 | 3.3.5 |
| `github.com/argoproj/argo-workflows/v3` | Go | From 3.3.0 | 3.3.5 |
| `argo-workflows` | Bitnami | From 2.6.0 | 3.2.11, 3.3.5 |

Products: Argoproj Argo Workflows.

## How do I fix CVE-2022-29164?

Upgrade github.com/argoproj/argo-workflows/v3 to a fixed version for your release line: 3.2.11 or 3.3.5.

## Is CVE-2022-29164 being exploited?

There is no known exploitation of CVE-2022-29164 in the wild and no public exploit code.

## Other vulnerabilities in argoproj argo-workflows

- [CVE-2026-28229](https://insights.sbomify.com/CVE-2026-28229/): Argo Workflows has unauthorized access to Argo Workflows Template (critical 9.8)
- [CVE-2026-54526](https://insights.sbomify.com/CVE-2026-54526/): Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing (high 8.9)
- [CVE-2026-31892](https://insights.sbomify.com/CVE-2026-31892/): WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode (high 8.9)
- [CVE-2026-42295](https://insights.sbomify.com/CVE-2026-42295/): Argo Workflows: Exposure of artifact repository credentials (high 8.5)
- [CVE-2026-42297](https://insights.sbomify.com/CVE-2026-42297/): Argo Workflows Is Missing Authorization in Sync ConfigMap Provider (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29164 and fix it if it is affected.

What it is: CVE-2022-29164 is a high-severity cross-site scripting vulnerability in argoproj argo-workflows, published on 5 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29164 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-workflows/v3 (Go): affected from 2.6.0; fixed in 3.2.11
- github.com/argoproj/argo-workflows/v3 (Go): affected from 2.6.0; fixed in 3.2.11
- github.com/argoproj/argo-workflows/v3 (Go): affected from 3.3.0; fixed in 3.3.5
- github.com/argoproj/argo-workflows/v3 (Go): affected from 3.3.0; fixed in 3.3.5
- argo-workflows (Bitnami): affected from 2.6.0; fixed in 3.2.11, 3.3.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29164/ (Markdown: https://insights.sbomify.com/CVE-2022-29164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29164
- OSV: https://osv.dev/vulnerability/CVE-2022-29164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29164/
Summaries are generated and may contain mistakes; the official description above is the record.