CVE-2026-31892: Argo Workflows security bypass via podSpecPatch in WorkflowTemplates

CVE-2026-31892 · Severity: high · CVSS 8.1 · Published 2026-03-11

Argo Workflows is an automation engine used to run complex parallel jobs on Kubernetes clusters. A security flaw allows users with permission to submit workflows to bypass administrative security restrictions by injecting custom configuration patches. This could allow an attacker to run unauthorized code with high privileges, potentially gaining access to sensitive data or the underlying host system.

Technologies: Argo Project Workflows, github.com/argoproj/argo-workflows (Go), github.com/argoproj/argo-workflows/v2 (Go), github.com/argoproj/argo-workflows/v3 (Go), github.com/argoproj/argo-workflows/v4 (Go). Vendors: Argo Project, Go.

Quick answers

Is CVE-2026-31892 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-31892 being exploited in the wild.
How severe is CVE-2026-31892?
High severity, with a CVSS score of 8.1, published 11 March 2026.
Which products and versions are affected?
Argo Project Workflows >= 2.9.0, < 3.7.11; >= 4.0.0, < 4.0.2; github.com/argoproj/argo-workflows (Go) SEMVER:introduced=0, SEMVER:introduced=2.9.0; github.com/argoproj/argo-workflows/v2 (Go) SEMVER:introduced=2.9.0; github.com/argoproj/argo-workflows/v3 (Go) SEMVER:introduced=0,fixed=3.7.11; and 1 more.
Is there a fix for CVE-2026-31892?
Yes. github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.7.11 or later; github.com/argoproj/argo-workflows/v4 (Go): upgrade to 4.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-31892 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-31892?
Check whether you run Argo Project Workflows, github.com/argoproj/argo-workflows (Go), github.com/argoproj/argo-workflows/v2 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/argoproj/argo-workflows/v3 (Go): upgrade to 3.7.11 or later
    go get github.com/argoproj/argo-workflows/v3@v3.7.11
  • github.com/argoproj/argo-workflows/v4 (Go): upgrade to 4.0.2 or later
    go get github.com/argoproj/argo-workflows/v4@v4.0.2

Technical details

A vulnerability in Argo Workflows arises from the way the controller merges workflow specifications. When a user submits a Workflow that references a WorkflowTemplate, the 'podSpecPatch' field in the user's submission takes precedence over the template's settings during the merge process in 'JoinWorkflowSpec'. The controller fails to perform security validation on the contents of this patch, and the 'templateReferencing: Strict' mode only verifies the presence of a template reference rather than restricting additional fields. Consequently, an authenticated user can inject dangerous Kubernetes PodSpec settings (e.g., privileged: true, hostPath mounts, or root UID) to bypass administrative guardrails. The issue is fixed in versions 3.7.11 and 4.0.2.

Affected products

  • argoproj Argo Workflows >= 2.9.0, < 3.7.11; >= 4.0.0, < 4.0.2
  • Red Hat OpenShift AI 2.25 Affected

Identifiers

  • CVE-2026-31892
  • GHSA-3wf5-g532-rcrr
  • GO-2026-4681

Timeline

  • 2026-03-11: disclosed
  • 2026-03-11: advisory
  • 2026-03-11: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.