Affected versions
Version ranges need review.
- Affected versions
- *
- Fixed version
- Not reported
- Affected versions
- *
- Fixed version
- Not reported
- Affected versions
- >= 4.0.0, < 4.0.5
- Fixed version
- 4.0.5
- Affected versions
- >=4.0.0 <4.0.5
- Fixed version
- 4.0.5
- Affected versions
- *
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
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.
Links
- https://github.com/advisories/GHSA-7vf8-2cr6-54mf
- https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24
- https://github.com/argoproj/argo-workflows/commit/bdd40908580f727c590c8743836e338b04fe4a87
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5
- 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://nvd.nist.gov/vuln/detail/CVE-2026-42295
Credits
- Masamuneee
- Joibel
- isubasinghe

