CVE-2026-42295: CWE-522: Insufficiently Protected Credentials in argoproj argo-workflows
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From version 4.0.0 to before version 4.0.5, the workflow executor logs all artifact repository credentials (S3 access keys, secret keys, GCS service account keys, Azure account keys, Git passwords, etc.) in plaintext on artifact operation. Any user with read access to workflow pod logs can extract these credentials. This issue has been patched in version 4.0.5.
AI Analysis
Technical Summary
Argo Workflows, an open source container-native workflow engine for Kubernetes, versions 4.0.0 to before 4.0.5 improperly log sensitive artifact repository credentials in plaintext during artifact operations. This includes credentials for S3, GCS, Azure, and Git. Because these credentials are exposed in pod logs, any user with read access to the logs can obtain them. The vulnerability is classified under CWE-522 (Insufficiently Protected Credentials). A patch addressing this issue was released in version 4.0.5. The CVSS 4.0 score is 8.5 (high severity), reflecting network attack vector, low attack complexity, no user interaction, and high impact on confidentiality and integrity.
Potential Impact
Exposure of plaintext credentials in workflow pod logs can lead to unauthorized access to artifact repositories and cloud services, potentially compromising sensitive data and workflows. The vulnerability affects all users running vulnerable versions who allow read access to pod logs. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Upgrade argo-workflows to version 4.0.5 or later, where this issue is patched. Since this is a cloud service component, the vendor manages remediation for hosted services, but users running self-managed instances must apply the update. Review and rotate any credentials that may have been exposed in logs prior to patching.
CVE-2026-42295: CWE-522: Insufficiently Protected Credentials in argoproj argo-workflows
Description
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From version 4.0.0 to before version 4.0.5, the workflow executor logs all artifact repository credentials (S3 access keys, secret keys, GCS service account keys, Azure account keys, Git passwords, etc.) in plaintext on artifact operation. Any user with read access to workflow pod logs can extract these credentials. This issue has been patched in version 4.0.5.
CVSS v4.0
Score 8.5high
Affected software
pkg:github/argoproj/argo-workflowsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Argo Workflows, an open source container-native workflow engine for Kubernetes, versions 4.0.0 to before 4.0.5 improperly log sensitive artifact repository credentials in plaintext during artifact operations. This includes credentials for S3, GCS, Azure, and Git. Because these credentials are exposed in pod logs, any user with read access to the logs can obtain them. The vulnerability is classified under CWE-522 (Insufficiently Protected Credentials). A patch addressing this issue was released in version 4.0.5. The CVSS 4.0 score is 8.5 (high severity), reflecting network attack vector, low attack complexity, no user interaction, and high impact on confidentiality and integrity.
Potential Impact
Exposure of plaintext credentials in workflow pod logs can lead to unauthorized access to artifact repositories and cloud services, potentially compromising sensitive data and workflows. The vulnerability affects all users running vulnerable versions who allow read access to pod logs. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Upgrade argo-workflows to version 4.0.5 or later, where this issue is patched. Since this is a cloud service component, the vendor manages remediation for hosted services, but users running self-managed instances must apply the update. Review and rotate any credentials that may have been exposed in logs prior to patching.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-26T12:13:55.552Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 69ffe1b2cbff5d8610ead43f
Added to database: 05/10/2026, 01:38:58 UTC
Last enriched: 05/17/2026, 10:46:04 UTC
Last updated: 07/01/2026, 20:51:20 UTC
Views: 73
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.