GitHub Advisoryadvisory · Go

GHSA-c2hv-4pfj-mm2r Argo Workflow may expose artifact repository credentials

HIGH Published 2025-10-14 Modified 2025-11-05 Official page ↗
Aliases
CVE-2025-62157
Ecosystem
Go
Packages
github.com/argoproj/argo-workflows/v3
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-522
Reviewed
2025-10-14

Affected packages

• Go github.com/argoproj/argo-workflows/v3: >= 3.7.0, < 3.7.3 → fixed in 3.7.3 • Go github.com/argoproj/argo-workflows/v3: < 3.6.12 → fixed in 3.6.12

Description

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. 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

Related

Alias · CVE (1)

  • CVE-2025-62157 Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. vulnerability

Weakness · CWE (1)

  • CWE-522 Insufficiently Protected Credentials weakness

References