Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-42294 high CVSS 7.5

Vulnerability in argo-workflows (CVE-2026-42294)

Summary

Vulnerability in argo-workflows (CVE-2026-42294). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/events/some-namespace. 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, the Webhook Interceptor loads the entire request body into memory before authenticating the request or verifying its signature. This occurs on the /api/v1/events/ endpoint, which is publicly accessible (albeit intended for webhooks). An attacker can send a request with an extremely large body (e.g., multiple gigabytes), causing the Argo Server to allocate excessive memory, potentially leading to an Out-Of-Memory (OOM) crash and denial of service. 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-42294 has been found in argo-workflows.
Attackers can target a specific entry point like POST /api/v1/events/some-namespace over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/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-42294" on the vendor's site.

CVE-2026-42294 (argo-workflows) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/events/some-namespace / io.ReadAll / http.MaxBytesReader
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

A vulnerability (CWE-770) exists in argo-workflows. Attackers reach the vulnerable code path via POST /api/v1/events/some-namespace without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of argo-workflows. Attack surface: POST /api/v1/events/some-namespace / io.ReadAll / http.MaxBytesReader.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 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 POST /api/v1/events/some-namespace requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect 
    grep 'POST /api/v1/events/some-namespace' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/events/some-namespace への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

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

    ステージング環境で 3.7.14, 4.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/v1/events/some-namespace on staging to confirm patch closes the vector

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

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