Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3

Argo Workflows affected by stored XSS in the artifact directory listing

CVE-2026-23960GHSA-cv78-6m8q-ph82

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-workflows/v3

    Affected
    < 3.6.17>= 3.7.0, <= 3.7.7
    Fixed in
    3.7.8, 3.6.17

  • Go github.com/argoproj/argo-workflows

    Affected
    <= 2.5.3-rc4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-23960: 0.41% estimated exploitation activity in the next 30 days; percentile 35.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. 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/artifactserver.go#L194-L244 PoC 1. Deploy Argo Workflows: 2. Port‑forward Argo Server: 3. Create the PoC workflow: 4. Wait for completion: 5. Get the node ID: 6. Open the listing: https://localhost:2746/artifact-files/argo/workflows/<wf-name/<node-id/outputs/dir/ <img width="1220" height="349" alt="image"…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-cv78-6m8q-ph82

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-23960

Advisory: Argo Workflows affected by stored XSS in the artifact directory listing
IDs: CVE-2026-23960, GHSA-cv78-6m8q-ph82
Record: https://patchnext.com/advisories/cve-2026-23960 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-workflows/v3 3.7.8, 3.6.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-workflows/v3: affected < 3.6.17; >= 3.7.0, <= 3.7.7; fixed in 3.7.8, 3.6.17
- Go github.com/argoproj/argo-workflows: affected <= 2.5.3-rc4

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-workflows/v3: check the installed version with your package manager.
- Go github.com/argoproj/argo-workflows: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-workflows/v3, github.com/argoproj/argo-workflows.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cv78-6m8q-ph82 (GitHub-reviewed advisory GHSA-cv78-6m8q-ph82 lists affected ranges: Go github.com/argoproj/argo-workflows/v3 >=0 =3.7.0 =0 <=2.5.3-rc4)

Commands are suggestions: review each one before running it.

Loading voting…