How severe is GHSA-cmv8-6362-r5w9?

GHSA-cmv8-6362-r5w9 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cmv8-6362-r5w9?

GHSA-cmv8-6362-r5w9 affects the following packages: github.com/argoproj/argo-workflows/v3 (Go), github.com/argoproj/argo-workflows/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-cmv8-6362-r5w9?

Update github.com/argoproj/argo-workflows/v3 to 3.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmv8-6362-r5w9 is resolved across your whole dependency graph.

How do I detect GHSA-cmv8-6362-r5w9 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-cmv8-6362-r5w9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cmv8-6362-r5w9?

O3 pinpoints whether GHSA-cmv8-6362-r5w9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-cmv8-6362-r5w9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cmv8-6362-r5w9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cmv8-6362-r5w9?

GHSA-cmv8-6362-r5w9 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 53th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cmv8-6362-r5w9?

GHSA-cmv8-6362-r5w9 is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cmv8-6362-r5w9 published, and has it been updated?

GHSA-cmv8-6362-r5w9 was published on May 23, 2022 and was last updated on March 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-cmv8-6362-r5w9

HIGH

Malicious HTML+XHR Artifact Privilege Escalation in Argo Workflows

Also known asBIT-argo-workflows-2022-29164CVE-2022-29164

Published

May 23, 2022

Updated

Mar 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk53th percentile+0.51%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐹github.com/argoproj/argo-workflows/v3🐹github.com/argoproj/argo-workflows/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 is very hard to exploit.

We urge all users to upgrade to the fixed versions. Disabling the Argo Server is the only known workaround. Note version 2.12 has been out of support for sometime. No fix is currently planned.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-workflows/v3`	≥ 2.6.0&&< 3.2.11	3.2.11
🐹Go	`github.com/argoproj/argo-workflows/v3`	≥ 3.3.0&&< 3.3.5	3.3.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/argoproj/argo-workflows/v3 to 3.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmv8-6362-r5w9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-cmv8-6362-r5w9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-cmv8-6362-r5w9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-cmv8-6362-r5w9 in your dependencies?

O3 detects GHSA-cmv8-6362-r5w9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works