argoproj argo-workflows up to 3.6.11/3.7.2 insufficiently protected credentials

Summaryinfo

A vulnerability marked as problematic has been reported in argoproj argo-workflows up to 3.6.11/3.7.2. This affects an unknown part. This manipulation causes insufficiently protected credentials. This vulnerability is tracked as CVE-2025-62157. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in argoproj argo-workflows up to 3.6.11/3.7.2 and classified as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. The CWE definition for the vulnerability is CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-62157 since 10/07/2025. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Upgrading to version 3.6.12 or 3.7.3 eliminates this vulnerability. Applying the patch 18ad5138b6bcb2aba04e00b4ec657bc6b8fad8df is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• argoproj

Name

• argo-workflows

Version

• 3.6.0
• 3.6.1
• 3.6.2
• 3.6.3
• 3.6.4
• 3.6.5
• 3.6.6
• 3.6.7
• 3.6.8
• 3.6.9
• 3.6.10
• 3.6.11
• 3.7.0
• 3.7.1
• 3.7.2

License

• open-source

Website

• Product: https://github.com/argoproj/argo-workflows/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion