Argo Workflows
Approved changes feed: RSS · Atom
cpe:2.3:a:argo_workflows_project:argo_workflows:*:*:*:*:*:kubernetes:*:*
part: a version: * update: *
| Vendor | Argo Workflows Project (dd15eefa-eda8-5544-aede-a39cd975bed4) |
|---|---|
| Product | Argo Workflows (9ee52e59-5c8a-5e28-9363-8374cfc16203) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | kubernetes |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/argoproj/argo-workflows |
purl2cpe | 2026-06-01 10:11:11.510554 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-29164 |
vulnerable | 2026-06-08 05:42:47.035628 |
Privilege Escalation in argo-workflows
HIGH (7.1)
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.
Published: 2022-05-05T23:15:12.000Z
Updated: 2025-04-23T18:30:26.977Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.