Argo Workflows (workflow executor, artifact driver logging): The executor logs the whole artifact driver struct, so S3

Impact

The executor logs the whole artifact driver struct, so S3 access keys, GCS service account keys, Azure account keys and Git passwords land in plaintext workflow pod logs. Any tenant with pod-log read in that namespace walks off with the artifact repository credentials and can read, overwrite or delete every other tenant's datasets and model artifacts. Incomplete fix of CVE-2025-62157, which covered the controller but not the executor.

Who can reach it

A user or service account with get/list on pods/log in a namespace where workflows run. No workflow submission rights needed.

What to do

Upgrade to 4.0.5 and restart controller and server so new executors ship the fixed logging. Then rotate the artifact repository credentials and tighten pods/log RBAC - the credentials are already in whatever log store scraped those pods.

References