# CVE-2025-62157: GO-2025-4024 - Argo Workflow may expose artifact repository credentials in github.com/argoproj/argo-workflows

Source: https://junglewise.ai/threats/cve-2025-62157-argo-workflow-may-expose-artifact-repository-credentials  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-14  
License: CC BY 4.0 with a link back

CVE-2025-62157 · Severity: medium · CVSS 6.5 · Published 2025-10-14

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Argo Workflows versions prior to 3.6.12 and versions 3.7.0 through 3.7.2 expose artifact repository credentials in plaintext in workflow-controller pod logs. An attacker with permissions to read pod logs in a namespace running Argo Workflows can read the workflow-controller logs and obtain credentials to the artifact repository. Update to versions 3.6.12 or 3.7.3 to remediate the vulnerability. No known workarounds exist.

Technologies: [github.com/argoproj/argo-workflows (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows), [github.com/argoproj/argo-workflows/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows-v2), [github.com/argoproj/argo-workflows/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-argoproj-argo-workflows-v3). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-62157 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-62157 being exploited in the wild.

**How severe is CVE-2025-62157?** Medium severity, with a CVSS score of 6.5, published 14 October 2025.

**Which products and versions are affected?** github.com/argoproj/argo-workflows (Go) SEMVER:introduced=0; github.com/argoproj/argo-workflows/v2 (Go) SEMVER:introduced=0; github.com/argoproj/argo-workflows/v3 (Go) SEMVER:introduced=0,fixed=3.6.12,introduced=3.7.0,fixed=3.7.3, SEMVER:introduced=3.7.0,fixed=3.7.3.

**Is there a fix for CVE-2025-62157?** Yes. github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.7.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-62157?** Check whether you run github.com/argoproj/argo-workflows (Go), github.com/argoproj/argo-workflows/v2 (Go) or github.com/argoproj/argo-workflows/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.7.3 or later

  ```sh
  go get github.com/argoproj/argo-workflows/v3@v3.7.3
  ```


## Affected products

- github.com/argoproj/argo-workflows (Go) SEMVER:introduced=0
- github.com/argoproj/argo-workflows/v2 (Go) SEMVER:introduced=0
- github.com/argoproj/argo-workflows/v3 (Go) SEMVER:introduced=0,fixed=3.6.12,introduced=3.7.0,fixed=3.7.3, SEMVER:introduced=3.7.0,fixed=3.7.3

## Identifiers

- CVE-2025-62157
- GHSA-c2hv-4pfj-mm2r
- GO-2025-4024

## Related threats

- [Argo Workflows privilege escalation via ArtifactGC PodSpecPatch](https://junglewise.ai/threats/cve-2026-54526-argo-workflows-privilege-escalation-via-artifactgc-podspecpatch)
- [Argo Workflows missing authorization in Sync ConfigMap Provider](https://junglewise.ai/threats/cve-2026-42297-argo-workflows-missing-authorization-in-sync-configmap-provider)
- [Argo Workflows authorization bypass in templateReferencing Strict mode](https://junglewise.ai/threats/cve-2026-42296-argo-workflows-authorization-bypass-in-templatereferencing-strict)
- [Argo Workflows plaintext credential leak in workflow logs](https://junglewise.ai/threats/cve-2026-42295-argo-workflows-plaintext-credential-leak-in-workflow-logs)
- [Argo Workflows denial of service in Webhook Interceptor](https://junglewise.ai/threats/cve-2026-42294-argo-workflows-denial-of-service-in-webhook-interceptor)