Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-42296 high CVSS 8.1

Authorization Flaw in argo-workflows (CVE-2026-42296)

Summary

Vulnerability in argo-workflows (CVE-2026-42296). Confidential information can be exposed externally. Mitigation: upgrade to 3.7.14, 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. Prior to versions 3.7.14 and 4.0.5, a user with create Workflow permission can bypass templateReferencing: Strict to get host network access, switch service accounts, override pod security context, add tolerations to schedule on control-plane nodes, or enable SA token mounting. This defeats the stated purpose of the feature. The practical impact depends on what Kubernetes-level controls are in place. Clusters with PodSecurity admission or OPA/Gatekeeper would independently block some of these (like hostNetwork). Clusters that rely on Argo's Strict mode as the primary enforcement layer are fully exposed. This issue has been patched in versions 3.7.14 and 4.0.5.

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-42296 has been found in argo-workflows.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade argo-workflows to 3.7.14, 4.0.5 or later.
If unsure, ask your IT team or search "argo-workflows CVE-2026-42296" on the vendor's site.

CVE-2026-42296 (argo-workflows) — CWE-863 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.7.14, 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

Incorrect authorization (CWE-863) exists in argo-workflows.

📍 Affected scope

Check the vendor advisory for the affected versions of argo-workflows.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.7.14, 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

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

  1. 1
    Identify exposure identify 
    grep -r 'argo-workflows' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade argo-workflows to 3.7.14, 4.0.5

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

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

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

Affected packages

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

References

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