Database/Container, Kubernetes & orchestration
Argo Workflows Helm chart (argo-helm, workflow-role privileges on workflowtasksets / workflowartifactgctasks): The
Impact
The chart hands workflowtasksets and workflowartifactgctasks permissions to every workflow pod when only agent and artifact-GC pods need them. A tenant workload can tamper with status reporting for other pods and templates. Impact is limited to status integrity, not code execution.
Who can reach it
A user who can get a workflow executed in the namespace, on argo-helm charts below 0.45.0.
What to do
Upgrade the argo-workflows Helm chart to 0.45.0 or later and apply. Roll it together with the 0.44.0 fix for CVE-2024-52799 - both are edits to the same workflow-role and land without a controller restart.
References
Related entries
- Kubernetes: Endpoint IPs can redirect pod traffic to private node networksCVE-2021-25737 · KubernetesLow
- Kubernetes (kube-apiserver): Init/ephemeral container envFrom bypasses the ServiceAccount mountable-secrets policyCVE-2024-3177 · Kubernetes (kube-apiserver)Low
- Kubernetes (kube-apiserver): Nodes can bypass DRA authorization checksCVE-2025-4563 · Kubernetes (kube-apiserver)Low
- Argo Workflows (Argo Server, SSO RBAC delegation gatekeeper): With SSO_DELEGATE_RBAC_TO_NAMESPACE enabled, an SSO userCVE-2026-42183 · Argo Workflows (Argo Server, SSO RBAC delegation gatekeeper)Low
- BuildKit: unbounded /etc/passwd read from a build image OOM-kills the buildkitd daemonCVE-2026-61712 · BuildKit buildkitd (user resolution in executor/oci/user.go)Low
- Kubernetes (kube-apiserver): TOCTOU/DNS-rebinding bypass of the link-local and localhost proxy protectionsCVE-2020-8562 · Kubernetes (kube-apiserver)Low
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.