جزئیات آسیب‌پذیری

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.

• https://github.com/argoproj/argo-workflows/commit/534f4ff1cbd86908e8ff76d97d553ad5a49a950d x_refsource_MISC
• https://github.com/argoproj/argo-workflows/releases/tag/v3.7.14 x_refsource_MISC
• https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5 x_refsource_MISC
• https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3775-99mw-8rp4 x_refsource_CONFIRM
• https://access.redhat.com/security/cve/CVE-2026-42296 vdb-entryx_refsource_REDHAT
• https://bugzilla.redhat.com/show_bug.cgi?id=2468446 issue-trackingx_refsource_REDHAT
• https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42296.json x_sadp-csaf-vex