Summary
Workarounds
- Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it.
This was identified by engineers at Jetstack.io
Impact
We are not aware of any exploits. This is a pro-active fix.
Impacted:
- You are running Argo Server < v3.0 with
--secure=trueor >= v3.0 with--secureunspecified (note - running in secure mode is recommended regardless). - The attacker is within your network. If you expose Argo Server to the Internet then "your network" is "the Internet".
The Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests.
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-6C73-2V8X-QPVM? GHSA-6C73-2V8X-QPVM is a medium-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-6C73-2V8X-QPVM? github.com/argoproj/argo-workflows/v3 (go) versions >= 3.0.0, < 3.0.9 is affected.
- Is there a fix for GHSA-6C73-2V8X-QPVM? Yes. GHSA-6C73-2V8X-QPVM is fixed in 3.0.9, 3.1.6. Upgrade to this version or later.
- Is GHSA-6C73-2V8X-QPVM exploitable, and should I be worried? Whether GHSA-6C73-2V8X-QPVM 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-6C73-2V8X-QPVM 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-6C73-2V8X-QPVM?
- 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