Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-28229 critical CVSS 9.8

Authorization Flaw in github.com/argoproj/argo-workflows/v4 (CVE-2026-28229)

Summary

Vulnerability in github.com/argoproj/argo-workflows/v4 (CVE-2026-28229). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.0.2 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 4.0.2 and 3.7.11, Workflow templates endpoints allow any client to retrieve WorkflowTemplates (and ClusterWorkflowTemplates). Any request with a Authorization: Bearer nothing token can leak sensitive template content, including embedded Secret manifests. This vulnerability is fixed in 4.0.2 and 3.7.11.

Source: GitHub Security Advisories (Global) 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-28229 has been found in github.com/argoproj/argo-workflows/v4.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/argoproj/argo-workflows/v4 to 4.0.2 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-workflows/v4 CVE-2026-28229" on the vendor's site.

CVE-2026-28229 (github.com/argoproj/argo-workflows/v4) — CWE-863 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.0.2 — 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

Incorrect authorization (CWE-863) exists in github.com/argoproj/argo-workflows/v4.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/argoproj/argo-workflows/v4.

🔥 Severity

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

🔧 How to fix

Update to 4.0.2.

🛡️ 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.2

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

  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":"0"},{"fixed":"4.0.2"}]}]
go github.com/argoproj/argo-workflows/v3
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.11"}]}]
Bitnami argo-workflows
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.7.11"},{"introduced":"4.0.0"},{"fixed":"4.0.2"}]}]

References

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