Incorrect Authorization Affecting argo-workflow-executor-compat-3.6 package, versions *


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Incorrect Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-ARGOWORKFLOWEXECUTORCOMPAT36-15562286
  • published14 Mar 2026
  • disclosed11 Mar 2026

Introduced: 11 Mar 2026

NewCVE-2026-31892  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest argo-workflow-executor-compat-3.6.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflow-executor-compat-3.6 package and not the argo-workflow-executor-compat-3.6 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.

CVSS Base Scores

version 3.1