Incorrect Authorization Affecting argo-workflows-3.6 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (35th 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 IDSNYK-MINIMOSLATEST-ARGOWORKFLOWS36-16424487
  • published6 May 2026
  • disclosed9 May 2026

Introduced: 6 May 2026

CVE-2026-42296  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest argo-workflows-3.6.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflows-3.6 package and not the argo-workflows-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. Prior to versions 3.7.14 and 4.0.5, a user with create Workflow permission can bypass templateReferencing: Strict to get host network access, switch service accounts, override pod security context, add tolerations to schedule on control-plane nodes, or enable SA token mounting. This defeats the stated purpose of the feature. The practical impact depends on what Kubernetes-level controls are in place. Clusters with PodSecurity admission or OPA/Gatekeeper would independently block some of these (like hostNetwork). Clusters that rely on Argo's Strict mode as the primary enforcement layer are fully exposed. This issue has been patched in versions 3.7.14 and 4.0.5.