GHSA-6c73-2v8x-qpvm
Argo Server TLS requests could be forged by attacker with network access
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
What each source reports
GitHub AdvisoriesNo score
Argo Server TLS requests could be forged by attacker with network access
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
- Record
GHSA-6c73-2v8x-qpvm- Updated
- 2026-11-02
OSVNo score
Argo Server TLS requests could be forged by attacker with network access
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
- Record
GHSA-6c73-2v8x-qpvm- Updated
- 2026-11-02
OSVGO-2022-0388No score
Argo Server TLS requests could be forged by attacker with network access in github.com/argoproj/argo-workflows
Argo Server TLS requests could be forged by attacker with network access in github.com/argoproj/argo-workflows
- Record
GO-2022-0388- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/argoproj/argo-workflows/v3Go | 3.0.0 up to 3.0.9 | 3.0.9 |
github.com/argoproj/argo-workflows/v3Go | 3.1.0 up to 3.1.6 | 3.1.6 |
github.com/argoproj/argo-workflowsGo | All versions | None known |
github.com/argoproj/argo-workflows/v2Go | All versions | None known |
github.com/argoproj/argo-workflows/v3Go | 3.0.0 up to 3.0.9, 3.1.0 up to 3.1.6 | 3.0.93.1.6 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-6c73-2v8x-qpvm is a vulnerability with no CVSS score yet in github.com/argoproj/argo-workflows, published August 23, 2021. No source lists public exploit code. Fixed in github.com/argoproj/argo-workflows/v3 3.0.9.