CVE-2026-28229: Argo Workflows has unauthorized access to Argo Workflows Template
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 4.0.2 and 3.7.11, Workflow templates endpoints allow any client to retrieve WorkflowTemplates (and ClusterWorkflowTemplates). Any request with a Authorization: Bearer nothing token can leak sensitive template content, including embedded Secret manifests. This vulnerability is fixed in 4.0.2 and 3.7.11.
Security readout for executives and security teams
Plain-English summary
Argo Workflows had a critical access-control flaw that could let an unauthenticated client read workflow templates. Those templates may contain sensitive operational data, including embedded Secret manifests. Organizations running affected Argo Workflows versions should treat this as urgent because exposed templates can reveal credentials or deployment details.
Executive priority
Prioritize remediation immediately for internet-facing or broadly reachable Argo Workflows deployments. The main business risk is credential or configuration disclosure that could enable follow-on compromise.
Technical view
Before Argo Workflows 4.0.2 and 3.7.11, WorkflowTemplate and ClusterWorkflowTemplate endpoints improperly allowed retrieval by any client using the described bearer-token condition. The issue maps to missing authorization and improper access control, with CVSS 9.8 and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where Argo Workflows API or UI endpoints are reachable by untrusted users or networks. The affected ranges are >=4.0.0 and <4.0.2, and versions before 3.7.11.
Exploitation context
The provided bundle says KEV is false and does not cite active exploitation. The weakness is network-reachable, low-complexity, requires no privileges or user interaction, and can disclose sensitive template content.
Researcher notes
Evidence supports a critical unauthorized template disclosure issue in Argo Workflows, fixed in 4.0.2 and 3.7.11. Sources identify CWE-306 and CWE-863. No source in the bundle confirms exploitation in the wild.
Mitigation direction
Upgrade Argo Workflows to 4.0.2, 3.7.11, or later.
Restrict Argo Workflows API and UI access to trusted networks while patching.
Review WorkflowTemplates and ClusterWorkflowTemplates for embedded Secret manifests or sensitive values.
Rotate secrets that may have been exposed through workflow templates.
Check Red Hat guidance if using downstream packaged Argo Workflows.
Validation and detection
Inventory Argo Workflows deployments and record exact running versions.
Confirm no deployment remains in the listed affected version ranges.
Review exposure of Argo Workflows endpoints to users, clusters, and networks.
Audit workflow templates for sensitive embedded content.
Review access logs for unexpected template retrieval activity.
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-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.
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.
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.
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.
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
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.