How severe is GHSA-6c73-2v8x-qpvm?

No CVSS score has been assigned to GHSA-6c73-2v8x-qpvm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6c73-2v8x-qpvm?

GHSA-6c73-2v8x-qpvm affects the following packages: github.com/argoproj/argo-workflows/v3 (Go), github.com/argoproj/argo-workflows/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-6c73-2v8x-qpvm?

Update github.com/argoproj/argo-workflows/v3 to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c73-2v8x-qpvm is resolved across your whole dependency graph.

How do I detect GHSA-6c73-2v8x-qpvm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6c73-2v8x-qpvm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6c73-2v8x-qpvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-6c73-2v8x-qpvm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6c73-2v8x-qpvm published, and has it been updated?

GHSA-6c73-2v8x-qpvm was published on August 23, 2021 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Argo Server TLS requests could be forged by attacker with network accessGHSA-6c73-2v8x-qpvm

GHSA-6c73-2v8x-qpvm is a security vulnerability in github.com/argoproj/argo-workflows/v3. A fix is available for github.com/argoproj/argo-workflows/v3 — see the affected versions and patch details below.

Also known asGO-2022-0388

Published

Aug 23, 2021

Updated

Aug 21, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/argoproj/argo-workflows/v3🐹github.com/argoproj/argo-workflows/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-workflows/v3`	≥ 3.0.0&&< 3.0.9	3.0.9`go get github.com/argoproj/argo-workflows/v3@v3.0.9`
🐹Go	`github.com/argoproj/argo-workflows/v3`	≥ 3.1.0&&< 3.1.6	3.1.6`go get github.com/argoproj/argo-workflows/v3@v3.1.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-workflows/v3 to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c73-2v8x-qpvm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-6c73-2v8x-qpvm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

Argo Server TLS requests could be forged by attacker with network accessGHSA-6c73-2v8x-qpvm

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-6c73-2v8x-qpvm in your dependencies?