Malicious HTML+XHR Artifact Privilege Escalation in Argo Workflows
CVE-2022-29164GHSA-cmv8-6362-r5w9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/argoproj/argo-workflows/v3 3.3.5, 3.2.11), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/argoproj/argo-workflows/v3
- Affected
- >= 2.6.0, < 3.2.11>= 3.3.0, < 3.3.5
- Fixed in
- 3.2.11, 3.3.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cmv8-6362-r5w9 lists affected ranges: Go github.com/argoproj/argo-workflows/v3 >=2.6.0 =3.3.0 <3.3.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
- EPSS
- CVE-2022-29164: 0.92% estimated exploitation activity in the next 30 days; percentile 60.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. The attacker creates a workflow that produces a HTML artifact that contains a 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 do the following (if the victim may): Read information about the victim’s workflows. Create or delete workflows. Notes: 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. They won’t be able to repeatedly probe due to the social engineering aspect. The attacker is likely leave an audit trail. We have seen no evidence of this in the wild. While the impact is high, it…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-cmv8-6362-r5w9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2022-29164 Advisory: Malicious HTML+XHR Artifact Privilege Escalation in Argo Workflows IDs: CVE-2022-29164, GHSA-cmv8-6362-r5w9 Record: https://patchnext.com/advisories/cve-2022-29164 (revision 1, source checked 26 Oct 2026, 15:14 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-workflows/v3 3.3.5, 3.2.11. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/argoproj/argo-workflows/v3: affected >= 2.6.0, < 3.2.11; >= 3.3.0, < 3.3.5; fixed in 3.2.11, 3.3.5 ## Suggested inspection (read-only) - Go github.com/argoproj/argo-workflows/v3: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/argoproj/argo-workflows/v3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-cmv8-6362-r5w9 (GitHub-reviewed advisory GHSA-cmv8-6362-r5w9 lists affected ranges: Go github.com/argoproj/argo-workflows/v3 >=2.6.0 =3.3.0 <3.3.5) Commands are suggestions: review each one before running it.
Loading voting…