Skip to content
Fencer Vulns
high 8.1

CVE-2026-42296 json

Argo Workflows has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure

published 2026-05-04 6 mo ago modified 2026-09-08 2 mo ago also BIT-argo-workflows-2026-42296 , EUVD-2026-28894 , GHSA-3775-99mw-8rp4 , GO-2026-5072

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-workflows/v3 3.7.14
  • go github.com/argoproj/argo-workflows/v4 4.0.5
  • bitnami argo-workflows 3.7.14, 4.0.5
  • argo_workflows_project argo_workflows 3.7.14, 4.0.5
  • argoproj argo_workflows 3.7.14, 4.0.5
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-42296 updated cvss 8.1

Argo Workflows: github.com/argoproj/argo-workflows: Argo Workflows: Privilege escalation via security control bypass

  • Red Hat OpenShift AI 3.3 rhoai/odh-ml-pipelines-driver-rhel9 1790128730, rhoai/odh-ml-pipelines-launcher-rhel9 1790128683, rhoai/odh-ml-pipelines-api-server-v2-rhel9 1790129051, rhoai/odh-ml-pipelines-persistenceagent-v2-rhel9 1790130666, rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel9 1790128656, rhoai/odh-data-science-pipelines-argo-argoexec-rhel9 1790132012, +1 more
    fixed: vendor fix RHSA-2026:73987
  • Red Hat OpenShift AI 3.3 rhoai/odh-cli-rhel9 1790070206, rhoai/rhai-cli-rhel9 1790070206, rhoai/odh-mlflow-rhel9 1789653606, rhoai/odh-trainer-rhel9 1790136369, rhoai/odh-maas-api-rhel9 1790131842, rhoai/odh-mlserver-rhel9 1789121365, +70 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
5 mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3775-99mw-8rp4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CISA ADP 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-workflows/v3
<3.7.14
3.7.14
go github.com/argoproj/argo-workflows/v4
>=4.0.0, <4.0.5
4.0.5
bitnami argo-workflows
<3.7.14
>=4.0.0, <4.0.5
3.7.14
4.0.5
go github.com/argoproj/argo-workflows
all versions
 no fix listed
go github.com/argoproj/argo-workflows/v2
all versions
 no fix listed

Affected products

  • argoproj argo-workflows
  • Red Hat Red Hat OpenShift AI (RHOAI)

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.