Argo Workflows is a container-native workflow engine for Kubernetes. In versions before 3.7.14 and 4.0.5, a user with create Workflow permission can bypass the templateReferencing: Strict enforcement, which is intended to restrict certain pod specifications. This bypass allows the user to escalate privileges by gaining host network access, switching service accounts, overriding pod security contexts, adding tolerations to schedule on control-plane nodes, or enabling service account token mounting. The vulnerability is classified as CWE-863 (Incorrect Authorization). The practical impact depends on additional Kubernetes admission controls like PodSecurity admission or OPA/Gatekeeper, which may block some of these actions independently. Clusters that rely primarily on Argo's Strict mode for enforcement are vulnerable. The issue is patched in Argo Workflows versions 3.7.14 and 4.0.5.

Successful exploitation allows a user with create Workflow permission to bypass security restrictions intended to limit pod capabilities, potentially leading to privilege escalation and unauthorized access to host network and service accounts. This can compromise cluster security depending on the presence or absence of Kubernetes-level admission controls. The vulnerability does not affect availability but has high impact on confidentiality and integrity.

This vulnerability is patched in Argo Workflows versions 3.7.14 and 4.0.5. Users should upgrade to these or later versions to remediate the issue. No vendor advisory indicates that no action is required or that the issue is otherwise mitigated. Clusters using Kubernetes admission controls such as PodSecurity admission or OPA/Gatekeeper may have partial mitigation but should still apply the patch for full protection.