Quick answers
- Is CVE-2026-93991 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93991 being exploited in the wild.
- How severe is CVE-2026-93991?
- High severity, with a CVSS score of 7.7, published 19 September 2026.
- Which products and versions are affected?
- Argo Project Argo Workflows 4.1.0 through 4.1.3.
- Is there a fix for CVE-2026-93991?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93991 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93991?
- Check whether you run Argo Project Argo Workflows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The ListArchivedWorkflows API endpoint fails to apply cluster-scoped authorization review when a metadata.namespace field selector uses the NotEquals operator, allowing an attacker with namespace-scoped list permissions to retrieve archived workflows outside their authorized namespace. The vulnerability exists because the normalization logic that switches to cluster-wide access checks for negated selectors was implemented for live workflows but missed in the archived workflow path. An attacker can construct a negated namespace field selector to enumerate and access archived workflows from unauthorized namespaces.
Affected products
- Argo Project Argo Workflows 4.1.0 through 4.1.3
Timeline
- 2026-09-19: disclosed