MediumGHSA-6c73-2v8x-qpvmGO-2022-0388

Argo Server TLS requests could be forged by attacker with network access

Published 23 Aug 2021 · Updated 21 Aug 2024

Is your project on an affected github.com/argoproj/argo-workflows/v3?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=3.0.0 <3.0.9
Fixed in
3.0.9
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.0.9
Affected
>=3.1.0 <3.1.6
Fixed in
3.1.6
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.1.6

Details

Impact

We are not aware of any exploits. This is a pro-active fix.

Impacted:

  • You are running Argo Server < v3.0 with --secure=true or >= v3.0 with --secure unspecified (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

Is GHSA-6c73-2v8x-qpvm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/argoproj/argo-workflows/v3, and gives you the command that fixes it.

More advisories for github.com/argoproj/argo-workflows/v3

  • LowCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) in github.com/argoproj/argo-workflows · 18 Aug 2026
  • HighCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) · 13 Aug 2026
  • LowCVE-2026-42297Argo has Missing Authorization in its Sync ConfigMap Provider in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42183Argo Affected by SSO RBAC Delegation Nil Pointer Dereference DoS (gatekeeper.go) in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42294Argo Vulnerable to Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42295Argo vulnerable to exposure of artifact repository credentials in github.com/argoproj/argo-workflows · 25 Jun 2026
All 33 advisories for github.com/argoproj/argo-workflows/v3

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.