Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Argo Server TLS requests could be forged by attacker with network access

GHSA-6c73-2v8x-qpvm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/argoproj/argo-workflows/v3 3.1.6, 3.0.9), redeploy, then verify what is actually installed.

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact We are not aware of any exploits. This is a pro-active fix. Impacted: You are running Argo Server < v3.0 with --secure=true or = v3.0 with --secure unspecified (note - running in secure mode is recommended regardless). The attacker is within your network. If you expose Argo Server to the Internet then "your network" is "the Internet". The Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests. Patches https://github.com/argoproj/argo-workflows/pull/6540 Workarounds Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it. This was identified by engineers at Jetstack.io

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

    Published from ghsa record GHSA-6c73-2v8x-qpvm

Agent brief

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

# Patch Next advisory brief: GHSA-6c73-2v8x-qpvm

Advisory: Argo Server TLS requests could be forged by attacker with network access
IDs: GHSA-6c73-2v8x-qpvm
Record: https://patchnext.com/advisories/ghsa-6c73-2v8x-qpvm (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-workflows/v3 3.1.6, 3.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-workflows/v3: affected >= 3.0.0, < 3.0.9; >= 3.1.0, < 3.1.6; fixed in 3.1.6, 3.0.9

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-workflows/v3.
- 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-6c73-2v8x-qpvm (GitHub-reviewed advisory GHSA-6c73-2v8x-qpvm lists affected ranges: Go github.com/argoproj/argo-workflows/v3 >=3.0.0 =3.1.0 <3.1.6)

Commands are suggestions: review each one before running it.

Loading voting…