# CVE-2026-23960: Argo Workflows affected by stored XSS in the artifact directory listing > Stored XSS in Argo Workflows allows attackers to execute arbitrary JavaScript in victims' browsers, enabling unauthorized API actions. - **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 21 Jan 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-argo-workflows-2026-23960, GHSA-cv78-6m8q-ph82, GO-2026-4350, MINI-2rq9-h44c-3w4m, MINI-7qqg-3mw8-gqg3, MINI-8chw-9q8q-3pmf, MINI-f3f7-67xg-28gp, MINI-v2qr-g8fv-wvrx, MINI-xfx2-w233-v5v8 ## What is CVE-2026-23960? CVE-2026-23960 is a high-severity cross-site scripting vulnerability in argoproj argo-workflows, published on 21 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2026-23960? 10 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v3, argo-workflows and github.com/argoproj/argo-workflows. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.6.17, 3.7.8 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.6.17 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.6.17 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.7.0 | 3.7.8 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.7.0 | 3.7.8 | | `argo-workflows` | Bitnami | All versions | 3.6.17, 3.7.8 | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows` | Go | All versions to 2.5.3-rc4 | None | | `github.com/argoproj/argo-workflows` | Go | All versions to 2.5.3-rc4 | None | | `github.com/argoproj/argo-workflows/v2` | Go | All versions | None | Products: Argoproj Argo Workflows. ## How do I fix CVE-2026-23960? Upgrade github.com/argoproj/argo-workflows/v3 to a fixed version for your release line: 3.6.17 or 3.7.8. ## Is CVE-2026-23960 being exploited? There is no known exploitation of CVE-2026-23960 in the wild and no public exploit code. ## Other vulnerabilities in argoproj argo-workflows - [CVE-2026-28229](https://insights.sbomify.com/CVE-2026-28229/): Argo Workflows has unauthorized access to Argo Workflows Template (critical 9.8) - [CVE-2026-54526](https://insights.sbomify.com/CVE-2026-54526/): Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing (high 8.9) - [CVE-2026-31892](https://insights.sbomify.com/CVE-2026-31892/): WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode (high 8.9) - [CVE-2026-42295](https://insights.sbomify.com/CVE-2026-42295/): Argo Workflows: Exposure of artifact repository credentials (high 8.5) - [CVE-2026-42297](https://insights.sbomify.com/CVE-2026-42297/): Argo Workflows Is Missing Authorization in Sync ConfigMap Provider (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-23960 and fix it if it is affected. What it is: CVE-2026-23960 is a high-severity cross-site scripting vulnerability in argoproj argo-workflows, published on 21 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-23960 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.6.17, 3.7.8 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.6.17 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.6.17 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.7.0; fixed in 3.7.8 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.7.0; fixed in 3.7.8 - argo-workflows (Bitnami): affected all versions; fixed in 3.6.17, 3.7.8 - github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows (Go): affected all versions up to 2.5.3-rc4; no fix listed - github.com/argoproj/argo-workflows (Go): affected all versions up to 2.5.3-rc4; no fix listed - github.com/argoproj/argo-workflows/v2 (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-23960/ (Markdown: https://insights.sbomify.com/CVE-2026-23960/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23960 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23960 - OSV: https://osv.dev/vulnerability/CVE-2026-23960 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-23960/ Summaries are generated and may contain mistakes; the official description above is the record.