CVE-2026-42295: Argo vulnerable to exposure of artifact repository credentials
Summary 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.
Published May 4, 2026 · Updated May 13, 2026
Affected packages
github.com/argoproj/argo-workflows/v4
- Ecosystem
- Go
- Affected
- >= 4.0.0, < 4.0.5
- Fixed in
- 4.0.5
- Check
go list -m github.com/argoproj/argo-workflows/v4
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Note: This is an incomplete fix of CVE-2025-62157
Details
The logging driver passes the entire ArtifactDriver struct to the structured logger, for example: https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24
Exposed credential fields:
- S3 (workflow/artifacts/s3/s3.go): AccessKey, SecretKey, SessionToken, ServerSideCustomerKey
- OSS (workflow/artifacts/oss/oss.go): AccessKey, SecretKey, SecurityToken
- GCS (workflow/artifacts/gcs/gcs.go): ServiceAccountKey
PoC
- Create template
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
name: cred-leak-test
namespace: argo
spec:
entrypoint: main
templates:
- name: main
container:
image: alpine:3.13
command: [sh, -c]
args: ["echo 'hello' > /tmp/output.txt"]
outputs:
artifacts:
- name: output
path: /tmp/output.txt
s3:
endpoint: minio:9000
insecure: true
bucket: my-bucket
key: test-output.txt
accessKeySecret:
name: my-minio-cred
key: accesskey
secretKeySecret:
name: my-minio-cred
key: secretkey- Then check the logs
kubectl -n argo logs "cred-leak-test" -c wait
Impact
Any user with Kubernetes RBAC permissions to read pod logs in the workflow namespace can extract artifact repository credentials.
Credited to Masamuneee, Joibel, isubasinghe.
References
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-7vf8-2cr6-54mf
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-c2hv-4pfj-mm2r
- https://github.com/argoproj/argo-workflows/commit/bdd40908580f727c590c8743836e338b04fe4a87
- https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5
- https://nvd.nist.gov/vuln/detail/CVE-2026-42295
- https://github.com/advisories/GHSA-7vf8-2cr6-54mf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-54526
Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892)
high8.9No fixAug 13, 2026CVE-2026-42183
Argo Affected by SSO RBAC Delegation Nil Pointer Dereference DoS (gatekeeper.go)
low2.3May 4, 2026CVE-2026-42294
Argo Vulnerable to Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor
high7.5May 4, 2026CVE-2026-42296
Argo has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure
high8.1May 4, 2026CVE-2026-42297
Argo has Missing Authorization in its Sync ConfigMap Provider
high8.5May 4, 2026CVE-2026-40886
Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows Controller
high7.7No fixApr 23, 2026
