# GO-2022-0405 - Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with…

Source: https://junglewise.ai/threats/go-2022-0405-potential-privilege-escalation-on-kubernetes-v1-19-when-42cf4f67  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-08-21  
License: CC BY 4.0 with a link back

Severity: info · Published 2024-08-21

Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client` in github.com/argoproj/argo-workflows

Technologies: [github.com/argoproj/argo-workflows (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows), [github.com/argoproj/argo-workflows/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows-v2), [github.com/argoproj/argo-workflows/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows-v3). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Informational severity, published 21 August 2024.

**Which products and versions are affected?** github.com/argoproj/argo-workflows (Go) SEMVER:introduced=0; github.com/argoproj/argo-workflows/v2 (Go) SEMVER:introduced=0; github.com/argoproj/argo-workflows/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.0.9,introduced=3.1.0,fixed=3.1.6.

**Is there a fix for This vulnerability?** Yes. github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.1.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected?** Check whether you run github.com/argoproj/argo-workflows (Go), github.com/argoproj/argo-workflows/v2 (Go) or github.com/argoproj/argo-workflows/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.1.6 or later

  ```sh
  go get github.com/argoproj/argo-workflows/v3@v3.1.6
  ```


## Affected products

- github.com/argoproj/argo-workflows (Go) SEMVER:introduced=0
- github.com/argoproj/argo-workflows/v2 (Go) SEMVER:introduced=0
- github.com/argoproj/argo-workflows/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.0.9,introduced=3.1.0,fixed=3.1.6

## Related threats

- [Argo Workflows privilege escalation via ArtifactGC PodSpecPatch](https://junglewise.ai/threats/cve-2026-54526-argo-workflows-privilege-escalation-via-artifactgc-podspecpatch)
- [Argo Workflows missing authorization in Sync ConfigMap Provider](https://junglewise.ai/threats/cve-2026-42297-argo-workflows-missing-authorization-in-sync-configmap-provider)
- [Argo Workflows authorization bypass in templateReferencing Strict mode](https://junglewise.ai/threats/cve-2026-42296-argo-workflows-authorization-bypass-in-templatereferencing-strict)
- [Argo Workflows plaintext credential leak in workflow logs](https://junglewise.ai/threats/cve-2026-42295-argo-workflows-plaintext-credential-leak-in-workflow-logs)
- [Argo Workflows denial of service in Webhook Interceptor](https://junglewise.ai/threats/cve-2026-42294-argo-workflows-denial-of-service-in-webhook-interceptor)
