LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Argo Workflows users who can create workflows may be able to bypass Argo's template referencing restrictions and request more powerful Kubernetes pod settings. In clusters relying on Argo Strict mode as the main guardrail, this can expose sensitive service accounts, host networking, or control-plane scheduling paths.

Executive priority

Treat as a high-priority Kubernetes platform control issue. Patch promptly where Argo Workflows is multi-tenant or delegated to developers, especially if admission controls are weak or service accounts carry sensitive permissions.

Technical view

Before Argo Workflows 3.7.14 and 4.0.5, an incomplete fix for CVE-2026-31892 allowed Workflow creators to bypass templateReferencing controls and set fields such as hostNetwork, securityContext, serviceAccountName, tolerations, and service account token mounting. The issue is CWE-863 with CVSS 8.1.

Likely exposure

Exposure is limited to Argo Workflows deployments below 3.7.14, or 4.0.x before 4.0.5, where users have create Workflow permission. Risk is highest when Kubernetes admission controls are absent and Argo Strict mode is treated as the primary enforcement layer.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Practical abuse requires an authenticated user with permission to create Workflows, then depends on whether Kubernetes PodSecurity, OPA, Gatekeeper, or similar controls independently block risky pod settings.

Researcher notes

Focus analysis on authorization boundaries between Argo templateReferencing enforcement and Kubernetes admission. Sources identify the bypassed fields and fixed versions, but do not provide evidence of public exploitation or full downstream vendor remediation coverage.

Mitigation direction

  • Upgrade Argo Workflows to 3.7.14 or 4.0.5.
  • Check vendor guidance for downstream package status.
  • Restrict create Workflow permission to trusted identities.
  • Enforce Kubernetes PodSecurity or OPA/Gatekeeper controls.
  • Block risky pod settings independently of Argo templates.
  • Review service account token mounting defaults.

Validation and detection

  • Inventory Argo Workflows versions across clusters.
  • List users and groups with create Workflow permission.
  • Confirm templateReferencing Strict or Secure mode is not the only guardrail.
  • Verify admission policies block hostNetwork and unsafe securityContext values.
  • Review recent Workflow specs for unexpected pod-level overrides.
  • Confirm upgraded deployments report 3.7.14 or 4.0.5.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-42296 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2GitHub_M
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-42296Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPArgo Workflows: github.com/argoproj/argo-workflows: Argo Workflows: Privilege escalation via security control bypass
other:Red Hat severity ratingcvssV3_1
  • 2026-05-09T05:01:27.119Z: Reported to Red Hat.
  • 2026-05-09T03:52:03.456Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
argoprojargo-workflows< 3.7.14, >= 4.0.0, < 4.0.5Listed
Weakness

CWE details

CWE-863

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs