Summary
Workarounds
None.
Impact
This is pro-active fix. No know exploits exist.
Impacted:
- You're running Kubernetes >= v1.19
- You're running Argo Server
- It is configured to with
--auth-mode=client - Is not configured with
--auth-mode=server - You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM.
- You're using client key to authenticate on the server.
- The server has more permissions that the connecting client's account.
The client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Frequently Asked Questions
- What is GHSA-PRQF-XR2J-XF65? GHSA-PRQF-XR2J-XF65 is a low-severity security vulnerability in github.com/argoproj/argo-workflows/v3 (go), affecting versions >= 3.0.0, < 3.0.9. It is fixed in 3.0.9, 3.1.6.
- Which versions of github.com/argoproj/argo-workflows/v3 are affected by GHSA-PRQF-XR2J-XF65? github.com/argoproj/argo-workflows/v3 (go) versions >= 3.0.0, < 3.0.9 is affected.
- Is there a fix for GHSA-PRQF-XR2J-XF65? Yes. GHSA-PRQF-XR2J-XF65 is fixed in 3.0.9, 3.1.6. Upgrade to this version or later.
- Is GHSA-PRQF-XR2J-XF65 exploitable, and should I be worried? Whether GHSA-PRQF-XR2J-XF65 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-PRQF-XR2J-XF65 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-PRQF-XR2J-XF65?
- Upgrade
github.com/argoproj/argo-workflows/v3to 3.0.9 or later - Upgrade
github.com/argoproj/argo-workflows/v3to 3.1.6 or later
- Upgrade