Privilege Escalation Vulnerability in Argo Workflows
Summary
GHSA-prqf-xr2j-xf65: Impact This is pro-active fix. Affects github.com/argoproj/argo-workflows/v3 across 2 version ranges.
>= 3.0.0, < 3.0.9
>= 3.1.0, < 3.1.6
Fixed in 3.0.9 or 3.1.6, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Argo Workflows is an open-source container-native workflow engine for orchestrating parallel jobs on Kubernetes. It allows users to define complex workflows using a declarative YAML syntax. Argo Workflows supports various authentication modes, including client authentication using a client key. However, a privilege escalation vulnerability has been identified when running Argo Server with the --auth-mode=client flag. This vulnerability affects Kubernetes versions 1.19 and above.
Vulnerability Detail
The privilege escalation vulnerability occurs when the Argo Server is configured with --auth-mode=client and is not running in a Kubernetes pod. If a client authenticates using a client key, the server will ignore the client's authentication and use its own authentication instead. This allows an attacker to escalate their privileges to that of the server's account. It is important to note that no known exploits of this vulnerability exist at the time of this advisory.
How To Fix
Latest published version: v3.7.18 as of 22 Oct 2026
go get github.com/argoproj/argo-workflows/v3@v3.7.18Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 3.0.0, < 3.0.93.0.9go get github.com/argoproj/argo-workflows/v3@v3.0.9 -
>= 3.1.0, < 3.1.63.1.6go get github.com/argoproj/argo-workflows/v3@v3.1.6
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There are no known workarounds for this vulnerability. It is recommended to apply the patch as soon as possible.
Conclusion
In conclusion, a privilege escalation vulnerability has been identified in Argo Workflows when running the Argo Server with --auth-mode=client. This vulnerability can be mitigated by upgrading to the patched versions of Argo Workflows. It is recommended to apply the patch as soon as possible to ensure the security of your Kubernetes environment. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/argoproj/argo-workflows/v3 →
FAQ
This vulnerability affects Kubernetes versions 1.19 and above.
The vulnerability occurs when the Argo Server is configured with --auth-mode=client.
No, this vulnerability can only be exploited when the Argo Server is running outside of a Kubernetes pod, such as on bare metal or other VM.
No, there are no known exploits of this vulnerability at the time of this advisory.
The vulnerability allows an attacker to escalate their privileges to that of the Argo Server's account.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/argoproj/argo-workflows/v3.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
