GHSA-6c73-2v8x-qpvm
GHSA-6c73-2v8x-qpvm is a security vulnerability in github.com/argoproj/argo-workflows/v3. O3 Security confirms whether GHSA-6c73-2v8x-qpvm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Argo Server TLS requests could be forged by attacker with network access
Real-World Exposure
github.com/argoproj/argo-workflows/v3🐹github.com/argoproj/argo-workflows/v3Real-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
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.
Patches
https://github.com/argoproj/argo-workflows/pull/6540
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-workflows/v3 | ≥ 3.0.0&&< 3.0.9 | 3.0.9 |
| 🐹Go | github.com/argoproj/argo-workflows/v3 | ≥ 3.1.0&&< 3.1.6 | 3.1.6 |
Detection & mitigation playbook
Open-source dependencyDetect
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.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c73-2v8x-qpvm 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-6c73-2v8x-qpvm 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-6c73-2v8x-qpvm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6c73-2v8x-qpvm in your dependencies?
O3 detects GHSA-6c73-2v8x-qpvm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.