Attack on Kubernetes via Misconfigured Argo Workflows
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/argoproj/argo-workflows (Go) | all versions | — | No fix listed | GHSA-rc7p-gmvh-xfx2 |
- github.com/argoproj/argo-workflows (Go) Vendor— Affected all versions Fixed in — No fix listed GHSA-rc7p-gmvh-xfx2
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-rc7p-gmvh-xfx2
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences