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
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
github.com/argoproj/argo-workflows/v3 to 3.7.3 or later; github.com/argoproj/argo-workflows/v3 to 3.6.12 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-62157? CVE-2025-62157 is a high-severity security vulnerability in github.com/argoproj/argo-workflows/v3 (go), affecting versions >= 3.7.0, < 3.7.3. It is fixed in 3.7.3, 3.6.12.
- Which versions of github.com/argoproj/argo-workflows/v3 are affected by CVE-2025-62157? github.com/argoproj/argo-workflows/v3 (go) versions >= 3.7.0, < 3.7.3 is affected.
- Is there a fix for CVE-2025-62157? Yes. CVE-2025-62157 is fixed in 3.7.3, 3.6.12. Upgrade to this version or later.
- Is CVE-2025-62157 exploitable, and should I be worried? Whether CVE-2025-62157 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-62157 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-62157?
- Upgrade
github.com/argoproj/argo-workflows/v3to 3.7.3 or later - Upgrade
github.com/argoproj/argo-workflows/v3to 3.6.12 or later
- Upgrade