Summary
Argo Workflows contains an authorization bypass in the archived workflow listing path when a namespace field selector uses the NotEquals operator. An attacker with namespace-scoped list permissions may retrieve archived workflows from other namespaces, including workflow arguments, parameter values, and annotations.
Affected context
The issue occurs in Argo Workflows deployments that expose archived workflow listing and rely on namespace-scoped authorization checks. Under affected conditions, a negated metadata.namespace field selector can cause the request to be evaluated without the expected cluster-scoped access review, potentially broadening the returned workflow set beyond the caller's authorized namespace.
Exploit preconditions
- Attack surface: The archived workflow listing API, specifically
ListArchivedWorkflows - Required access: Namespace-scoped permission to list archived workflows
- Trigger point: A list request using a
metadata.namespacefield selector with theNotEqualsoperator - Why exploitation is possible: The authorization logic does not consistently apply cluster-scoped access review for this selector form, allowing results from namespaces outside the caller's authorized scope
Why this happens
The underlying flaw is an authorization decision error involving a user-controlled resource selector. The access-control path treats a negated namespace condition differently from an ordinary namespace filter and fails to enforce the required cluster-scoped review. This maps to CWE-639: Authorization Bypass Through User-Controlled Key, because attacker-controlled selection criteria influence which protected records are returned without equivalent authorization enforcement.
Potential impact
- Unauthorized disclosure of archived workflows from other namespaces may occur
- Workflow arguments and parameter values could be exposed
- Annotations containing operational or sensitive metadata may be disclosed
- Cross-tenant or cross-team information boundaries could be weakened
- Exposed workflow data could support further reconnaissance or targeted attacks
General mitigation guidance
Mitigation generally focuses on making authorization independent of selector syntax and enforcing the narrowest applicable scope by default.
Common defensive patterns include:
- Apply authorization checks consistently for positive and negated field selectors
- Treat user-controlled selectors as filtering inputs rather than authorization evidence
- Enforce namespace and cluster-scope boundaries before returning any records
- Use deny-by-default behavior when selector scope cannot be resolved safely
- Minimize the sensitivity of archived workflow arguments, parameters, and annotations
- Run workflow services with only the permissions required for their operational role
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review of authorization branches involving selector operators
- Tests that compare access-control results for equivalent positive and negated namespace filters
- Policy checks requiring authorization before query filtering or result expansion
- API audit-log searches for namespace-exclusion selectors issued by namespace-scoped identities
- Regression tests confirming that archived workflow responses never cross authorized namespace boundaries
Automated security review tools may help identify inconsistent authorization paths, but behavioral access-control testing remains important.

