CVE-2026-93991 argoproj CVE debrief

Who should care

Defenders responsible for Argo Workflows deployments should assess exposure and prioritize verification and mitigation efforts. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-93991 is an authorization bypass vulnerability in Argo Workflows that allows attackers to retrieve archived workflows from other namespaces, potentially exposing sensitive information. Defenders should prioritize verification, assessment, and mitigation efforts.

• Potential exposure of sensitive information such as spec arguments, parameter values, and annotations
• Possible unauthorized access to archived workflows
• Need for verification of vulnerability presence in environment
• Priority for applying patches or mitigations

Technical summary

The vulnerability is caused by the failure of the ListArchivedWorkflows function to apply cluster-scoped access review when using the NotEquals operator with the metadata.namespace field selector. This allows attackers with namespace-scoped list permissions to retrieve archived workflows from other namespaces, potentially exposing sensitive information such as spec arguments, parameter values, and annotations. The vulnerability affects Argo Workflows versions 4.1.0 through 4.1.3, and defenders should prioritize verifying the vulnerability in their environment, assessing exposure, and applying patches or mitigations as needed.

Defensive priority

Defenders should prioritize verifying the vulnerability in their environment, assessing exposure, and applying patches or mitigations as needed.

Recommended defensive actions

• Verify the vulnerability in your environment
• Assess exposure and potential impact
• Apply patches or mitigations as needed
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is confirmed in Argo Workflows versions 4.1.0 through 4.1.3. The CVE record and NVD entry provide details on the vulnerability, but additional information may be needed to fully assess the impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.