CVE-2026-23960: Argo Workflows affected by stored XSS in the artifact directory listing
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to versions 3.6.17 and 3.7.8, stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges. Versions 3.6.17 and 3.7.8 fix the issue.
Security readout for executives and security teams
Plain-English summary
Argo Workflows versions before 3.6.17 and 3.7.8 can let a workflow author plant JavaScript that runs when another user views an artifact directory listing. That code runs as the Argo Server site and may perform API actions using the viewer’s privileges.
Executive priority
Prioritize patching within the normal high-severity remediation window, faster for shared or multi-tenant Argo deployments. This is not confirmed exploited in the provided evidence, but the privilege impact can be material.
Technical view
CVE-2026-23960 is stored XSS in Argo Workflows artifact directory listing, classified as CWE-79. The affected ranges are <3.6.17 and >=3.7.0,<3.7.8. CVSS 4.0 is 7.3 high, with low privileges required and user interaction required.
Likely exposure
Kubernetes environments running Argo Workflows with Argo Server and artifact browsing are the likely exposure point. Risk is higher where many users can author workflows and higher-privileged users browse workflow artifacts.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires a workflow author role and another user viewing the affected artifact listing. Successful abuse could trigger Argo API actions as that user.
Researcher notes
The key security boundary is browser execution under the Argo Server origin. The advisory indicates API actions may occur with victim privileges. Do not assume broader Kubernetes compromise without environment evidence and Argo authorization context.
Mitigation direction
Upgrade Argo Workflows to 3.6.17 or 3.7.8.
Restrict workflow author permissions until all clusters are patched.
Limit Argo Server access to trusted users and networks during remediation.
Review vendor and Red Hat guidance for environment-specific impact.
Audit recent artifact browsing by privileged Argo users if exposure existed.
Validation and detection
Inventory Argo Workflows versions across all Kubernetes clusters.
Identify Argo Server instances exposing artifact directory listings.
Confirm whether versions fall below 3.6.17 or between 3.7.0 and 3.7.7.
Review workflow author roles and who can create artifacts.
Confirm upgraded deployments report 3.6.17, 3.7.8, or later fixed releases.
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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 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
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.