Argo Workflows is a widely used open-source container-native workflow engine designed for orchestrating parallel jobs on Kubernetes. The vulnerability identified as CVE-2026-31892 stems from incorrect authorization controls (CWE-863) in how Argo Workflows merges workflow specifications. Specifically, from versions 2.9.0 up to but not including 3.7.11, and from 4.0.0 up to but not including 4.0.2, a user with the ability to submit workflows can include a podSpecPatch field in their workflow submission. This podSpecPatch overrides the pod specification defined in the referenced WorkflowTemplate during the spec merging process. Critically, this override bypasses all security settings and validations intended to restrict users to admin-approved templates, even when the controller is configured with templateReferencing set to Strict. The podSpecPatch is applied directly to the pod spec at creation time without any security validation, allowing malicious users to escalate privileges or execute unauthorized actions within the Kubernetes cluster. The vulnerability has been assigned a CVSS 4.0 base score of 8.9, indicating a high severity level. It requires low privileges (workflow submission rights), no user interaction, and can be exploited remotely over the network. Although no known exploits have been reported in the wild, the flaw presents a significant risk to environments running affected versions. The issue was fixed in Argo Workflows versions 3.7.11 and 4.0.2 by enforcing proper authorization checks and validation of podSpecPatch usage.

This vulnerability allows an attacker with workflow submission privileges to bypass security controls and inject arbitrary pod specifications, potentially leading to privilege escalation within Kubernetes clusters. The attacker can override security policies, run unauthorized containers, or escalate access beyond intended boundaries. This compromises the confidentiality and integrity of workloads and may lead to lateral movement, data exfiltration, or disruption of services. Since Argo Workflows is often used in CI/CD pipelines and production orchestration, exploitation could undermine the security of critical infrastructure and applications. The impact is heightened in environments where strict template referencing is relied upon for security governance, as this mechanism is rendered ineffective by the vulnerability. Organizations using affected versions face risks of unauthorized code execution, container escape, or deployment of malicious workloads, which can have cascading effects on cloud-native infrastructure and business operations.

Organizations should immediately upgrade Argo Workflows to version 3.7.11 or 4.0.2 or later, where the vulnerability is fixed. Until upgrades are applied, restrict workflow submission permissions to trusted users only and audit existing permissions to minimize exposure. Implement network segmentation and Kubernetes RBAC policies to limit the blast radius of compromised accounts. Monitor workflow submissions for unexpected podSpecPatch usage or anomalous pod specifications. Employ admission controllers or policy enforcement tools such as OPA Gatekeeper or Kyverno to validate and restrict podSpecPatch fields in workflows. Regularly review and harden Kubernetes cluster security configurations, including Pod Security Policies or Pod Security Admission to prevent privilege escalation. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises. Finally, stay informed on Argo Workflows security advisories and apply patches promptly.