HighGHSA-c2hv-4pfj-mm2rBIT-argo-workflows-2025-62157CVE-2025-62157GO-2025-4024

Argo Workflow may expose artifact repository credentials

Published 14 Oct 2025 · Updated 10 Sept 2026

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.7.0 <3.7.3
Fixed in
3.7.3
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.7.3
Affected
<3.6.12
Fixed in
3.6.12
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.6.12

Details

Summary

An attacker who has permissions to read logs from pods in a namespace with Argo Workflow can read workflow-controller logs and get credentials to the artifact repository.

Details

An attacker, by reading the logs of the workflow controller pod, can access the artifact repository, and steal, delete or modify the data that resides there. The workflow-controller logs show the credentials in plaintext.

<img width="1366" alt="screen" src="https://github.com/user-attachments/assets/5642b2be-edcf-4050-bf47-747d05352698" />

Impact

An attacker with access to pod logs in the argo namespace can extract plaintext credentials from the workflow-controller logs and gain access to the artifact repository. This can lead to:

  • Data exfiltration – theft of sensitive or proprietary artifacts
  • Data tampering – modification of workflows or artifacts
  • Data destruction – deletion of stored artifacts, leading to potential loss of critical data or pipeline failure

Is GHSA-c2hv-4pfj-mm2r 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.