Categories
CVE-2026-40886 high CVSS 7.7

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

Summary

Vulnerability in github.com/argoproj/argo-workflows/v4 (CVE-2026-40886). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.0.5 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. From 3.6.5 to 4.0.4, an unchecked array index in the pod informer's podGCFromPod() function causes a controller-wide panic when a workflow pod carries a malformed workflows.argoproj.io/pod-gc-strategy annotation. Because the panic occurs inside an informer goroutine (outside the controller's recover() scope), it crashes the entire controller process. The poisoned pod persists across restarts, causing a crash loop that halts all workflow processing until the pod is manually deleted. This vulnerability is fixed in 4.0.5 and 3.7.14.

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-40886 has been found in github.com/argoproj/argo-workflows/v4.
Risk of unauthorized operations or information disclosure. CVSS score: 7.7/10.
What to do: upgrade github.com/argoproj/argo-workflows/v4 to 4.0.5 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-workflows/v4 CVE-2026-40886" on the vendor's site.

CVE-2026-40886 (github.com/argoproj/argo-workflows/v4) — CWE-129 / CVSS v3 7.7
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-129) 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: High (CVSS 7.7/10). Risk of unauthorized operations or information disclosure.

🔧 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 '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.5

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

  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.5"}]}]
Go github.com/argoproj/argo-workflows/v3
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.14"}]}]
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":"3.6.5"},{"fixed":"3.7.14"},{"introduced":"4.0.0"},{"fixed":"4.0.5"}]}]

References

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