What is CVE-2026-93991?
Argo Workflows versions 4.1.0 through 4.1.3 contain an authorization bypass vulnerability in ListArchivedWorkflows that fails to apply cluster-scoped access review when the metadata.namespace field selector uses the NotEquals operator. Attackers with namespace-scoped list permissions can use a negated namespace field selector to retrieve archived workflows from all other namespaces, exposing spec arguments, parameter values, and annotations.
The record classifies CVE-2026-93991 under weakness class CWE-639. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 16 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.7 — HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - CVSS v4.0 base score
- 8.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N - EPSS (FIRST)
- 0.3% probability of exploitation in the next 30 days, higher than 25.9% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-19
Is CVE-2026-93991 being exploited?
It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.
Affected products and versions
- argoproj: argo-workflows
How to fix CVE-2026-93991
No vendor patch reference has been recorded for CVE-2026-93991 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-93991
No threat campaign in the Threadlinqs corpus currently references CVE-2026-93991, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .