How severe is GHSA-rc7p-gmvh-xfx2?

No CVSS score has been assigned to GHSA-rc7p-gmvh-xfx2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rc7p-gmvh-xfx2?

GHSA-rc7p-gmvh-xfx2 affects the following packages: github.com/argoproj/argo-workflows (Go). Ecosystems affected: Go.

How do I fix GHSA-rc7p-gmvh-xfx2?

No patched version of github.com/argoproj/argo-workflows has shipped for GHSA-rc7p-gmvh-xfx2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-rc7p-gmvh-xfx2 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rc7p-gmvh-xfx2 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-rc7p-gmvh-xfx2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rc7p-gmvh-xfx2 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-rc7p-gmvh-xfx2 published, and has it been updated?

GHSA-rc7p-gmvh-xfx2 was published on August 2, 2021 and was last updated on August 2, 2021. 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

Attack on Kubernetes via Misconfigured Argo WorkflowsGHSA-rc7p-gmvh-xfx2

GHSA-rc7p-gmvh-xfx2 is a remote code execution vulnerability in github.com/argoproj/argo-workflows. No vendor fix is recorded yet; mitigation options are listed below.

Published

Aug 2, 2021

Updated

Aug 2, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 2, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/argoproj/argo-workflows

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

Users running using the Argo Server with --auth-mode=server (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.

Resolution

Do not expose your user interface to the Internet.
Change configuration. --auth-mode=client.

For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-workflows`	all versions	No fix

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/argoproj/argo-workflows has shipped for GHSA-rc7p-gmvh-xfx2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 Users running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining. ### Resolution * Do not expose your user interface to the Internet. * Change configuration. `--auth-mode=client`. For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.

O3 Security · Impact-Aware SCA

Is GHSA-rc7p-gmvh-xfx2 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works