# CVE-2025-62157: argo-workflows — Fixed in 3.7.3 🐹 Go Not in CISA KEV # CVE-2025-62157 — argo-workflows [Fix: argoproj/argo-workflows@18ad513](https://github.com/argoproj/argo-workflows/commit/18ad5138b6bcb2aba04e00b4ec657bc6b8fad8df) CVE-2025-62157 is a CWE-522 vulnerability in github.com/argoproj/argo-workflows/v3. A fix is available for github.com/argoproj/argo-workflows/v3 — see the affected versions and patch details below. Argo Workflows exposes artifact repository credentials in workflow-controller logs Also known asBIT-argo-workflows-2025-62157[GHSA-c2hv-4pfj-mm2r](/vulnerability/GHSA-c2hv-4pfj-mm2r)GO-2025-4024 Published Oct 14, 2025 Updated Oct 28, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-62157. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.5%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk 0.00%0.32%0.64%0.97%0.0%0.5%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 2 pkgs affected 🐹`github.com/argoproj/argo-workflows/v3`🐹`github.com/argoproj/argo-workflows/v3` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems. ## 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. screen #### 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 Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix 🐹Go `github.com/argoproj/argo-workflows/v3` ≥ 3.7.0&&< 3.7.3 3.7.3`go get github.com/argoproj/argo-workflows/v3@v3.7.3` 🐹Go `github.com/argoproj/argo-workflows/v3` all versions 3.6.12`go get github.com/argoproj/argo-workflows/v3@v3.6.12` ## Affected Products 1 product · 2 configurations Application `argo workflows`argoproj ≥ 3.7.0 && < 3.7.3 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update github.com/argoproj/argo-workflows/v3 to 3.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62157 is resolved across your whole dependency graph. 3. ### Workarounds If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatModerate Workaround published by Red Hat > Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Source: [Red Hat security advisory for CVE-2025-62157](https://access.redhat.com/security/cve/cve-2025-62157) (CC BY 4.0) ## Frequently Asked Questions \### 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. screen ### Impact An attacker with access to pod logs in the \` O3 Security · Impact-Aware SCA ### Is CVE-2025-62157 in your dependencies? Find it across Go, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)