Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54526 critical CVSS 9.9

Vulnerability in github.com/argoproj/argo-workflows/v4 (CVE-2026-54526)

Summary

Vulnerability in github.com/argoproj/argo-workflows/v4 (CVE-2026-54526). Successful exploitation can lead to full system takeover. Exploitable via hostNetwork. Mitigation: upgrade to 4.0.6 or later.

Original description

The description as published by the source.

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54526 has been found in github.com/argoproj/argo-workflows/v4.
Attackers can target a specific entry point like hostNetwork over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/argoproj/argo-workflows/v4 to 4.0.6 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-workflows/v4 CVE-2026-54526" on the vendor's site.

CVE-2026-54526 (github.com/argoproj/argo-workflows/v4) — CWE-284 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: hostNetwork / securityContext / serviceAccountName / ValidateUserOverrides
Patched: 4.0.6 — 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-284) exists in github.com/argoproj/argo-workflows/v4. Attackers reach the vulnerable code path via hostNetwork.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/argoproj/argo-workflows/v4. Attack surface: hostNetwork / securityContext / serviceAccountName / ValidateUserOverrides.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.0.6.

🛡️ 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 'github.com/argoproj/argo-workflows/v4' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/argoproj/argo-workflows/v4' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/argoproj/argo-workflows/v4 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/argoproj/argo-workflows/v4 to 4.0.6

    ステージング環境で 4.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/argoproj/argo-workflows/v4
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.0.6"}]}]
go github.com/argoproj/argo-workflows/v3
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.7.15"}]}]
go github.com/argoproj/argo-workflows
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/argoproj/argo-workflows/v2
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Bitnami argo-workflows
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.7.15"},{"introduced":"4.0.0"},{"fixed":"4.0.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details