CVE-2026-23960: Argo Workflows affected by stored XSS in the artifact directory listing
Summary 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. Details The directory listing response in server/artifacts/artifactserver.go renders object names directly into HTML via fmt.Fprintf without escaping.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
github.com/argoproj/argo-workflows/v3
- Ecosystem
- Go
- Affected
- < 3.6.17
- Fixed in
- 3.6.17
- Check
go list -m github.com/argoproj/argo-workflows/v3
github.com/argoproj/argo-workflows/v3
- Ecosystem
- Go
- Affected
- >= 3.7.0, <= 3.7.7
- Fixed in
- 3.7.8
- Check
go list -m github.com/argoproj/argo-workflows/v3
github.com/argoproj/argo-workflows
- Ecosystem
- Go
- Affected
- <= 2.5.3-rc4
- Fixed in
- No patched version yet
- Check
go list -m github.com/argoproj/argo-workflows
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
The directory listing response in server/artifacts/artifact_server.go renders object names directly into HTML via fmt.Fprintf without escaping. Object names come from driver.ListObjects(...) and are attacker‑controlled when a workflow writes files into an output artifact directory.
https://github.com/argoproj/argo-workflows/blob/9872c296d29dcc5e9c78493054961ede9fc30797/server/artifacts/artifact_server.go#L194-L244
PoC
- Deploy Argo Workflows:
kubectl create ns argo
kubectl apply --server-side -f manifests/base/crds/full
kubectl apply --server-side -k manifests/quick-start/postgres- Port‑forward Argo Server:
kubectl -n argo port-forward deploy/argo-server 2746:2746- Create the PoC workflow:
cat > /tmp/argo-xss.yaml <<'EOF'
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: xss-artifact-test-
spec:
entrypoint: main
templates:
- name: main
container:
image: alpine
command: [sh, -c]
args:
- |
mkdir -p /tmp/artifacts
touch '/tmp/artifacts/xss">.html'
outputs:
artifacts:
- name: dir
path: /tmp/artifacts
archive:
none: {}
EOFkubectl -n argo create -f /tmp/argo-xss.yaml- Wait for completion:
kubectl -n argo get wf -w- Get the node ID:
kubectl -n argo get wf <wf-name> \
-o jsonpath='{range .status.nodes.*}{.id}{"\t"}{.displayName}{"\n"}{end}'- Open the listing:
https://localhost:2746/artifact-files/argo/workflows/<wf-name>/<node-id>/outputs/dir/
Impact
- The attacker creates a workflow that produces a HTML artifact that contains a HTML file that contains a script which uses XHR calls to interact with the Argo Server API.
- The attacker emails the deep-link to the artifact to their victim. The victim opens the link, the script starts running.
As the script has access to the Argo Server API (as the victim), so may do the following (if the victim may):
- Read information about the victim’s workflows.
- Create or delete workflows.
Credited to Masamuneee.
References
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-cv78-6m8q-ph82
- https://github.com/argoproj/argo-workflows/commit/159a5c56285ecd4d3bb0a67aeef4507779a44e17
- https://github.com/argoproj/argo-workflows/blob/9872c296d29dcc5e9c78493054961ede9fc30797/server/artifacts/artifact_server.go#L194-L244
- https://github.com/argoproj/argo-workflows/releases/tag/v3.6.17
- https://github.com/argoproj/argo-workflows/releases/tag/v3.7.8
- https://nvd.nist.gov/vuln/detail/CVE-2026-23960
- https://github.com/advisories/GHSA-cv78-6m8q-ph82
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-54526
Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892)
high8.9No fixAug 13, 2026CVE-2026-42294
Argo Vulnerable to Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor
high7.5May 4, 2026CVE-2026-42296
Argo has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure
high8.1May 4, 2026CVE-2026-40886
Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows Controller
high7.7No fixApr 23, 2026CVE-2026-28229
Unauthorized access to Argo Workflows Template
high7.5Mar 11, 2026CVE-2026-31892
Argo Workflows: WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
high8.9No fixMar 11, 2026
