← Back
CVE-2026-42295
medium
CVSS 4.9
Vulnerability in argo-workflows (CVE-2026-42295)
Summary
vulnerability in argo-workflows (CVE-2026-42295). Confidential information can be exposed externally. Mitigation: upgrade to `4.0.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42295** has been found in argo-workflows.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: upgrade argo-workflows to **4.0.5** or later.
If unsure, ask your IT team or search "argo-workflows CVE-2026-42295" on the vendor's site.
CVE-2026-42295 (argo-workflows) — CWE-522 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Patched: `4.0.5` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-522) exists in argo-workflows.
📍 Affected scope
argo-workflows — .
🔥 Severity
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.0.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'argo-workflows' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'argo-workflows' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `argo-workflows` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade argo-workflows to 4.0.5ステージング環境で 4.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
argo-workflows
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.0.5"}]}]
Go
github.com/argoproj/argo-workflows/v4
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.0.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42295
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- package https://github.com/argoproj/argo-workflows
- web [email protected]
- web https://github.com/argoproj/argo-workflows/security/advisories/GHSA-c2hv-4pfj-mm2r
- web https://github.com/argoproj/argo-workflows/commit/bdd40908580f727c590c8743836e338b04fe4a87
- web https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24
- web https://github.com/advisories/GHSA-7vf8-2cr6-54mf