# CVE-2026-42294: Argo Workflows: Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor > Unauthenticated attackers can cause denial of service in Argo Workflows by sending large payloads to the webhook endpoint, exhausting server memory. - **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 May 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-argo-workflows-2026-42294, ECHO-9dd3-fd4f-da54, GHSA-jcc8-g2q4-9fxq, GO-2026-5462, MINI-4fh2-cg3m-6q93, MINI-98fq-x88p-g833, MINI-fx94-gjmv-qq56, MINI-g24w-p438-wvgc, MINI-jgfg-q5mj-v463, MINI-qpjx-ff2v-9m28, MINI-wxjx-rh5p-4h83, MINI-xwxx-53jg-98r6, ROOT-APP-GOBINARY-CVE-2026-42294 ## What is CVE-2026-42294? CVE-2026-42294 is a high-severity denial of service vulnerability in argoproj argo-workflows, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2026-42294? 9 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v3, argo-workflows and github.com/argoproj/argo-workflows. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.14 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.14 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.14 | | `argo-workflows` | Bitnami | All versions | 3.7.14, 4.0.5 | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v2` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | Products: Argoproj Argo Workflows. ## How do I fix CVE-2026-42294? Upgrade github.com/argoproj/argo-workflows/v3 to 3.7.14 or later. ## Is CVE-2026-42294 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42294 exists. ## Other vulnerabilities in argoproj argo-workflows - [CVE-2026-28229](https://insights.sbomify.com/CVE-2026-28229/): Argo Workflows has unauthorized access to Argo Workflows Template (critical 9.8) - [CVE-2026-54526](https://insights.sbomify.com/CVE-2026-54526/): Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing (high 8.9) - [CVE-2026-31892](https://insights.sbomify.com/CVE-2026-31892/): WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode (high 8.9) - [CVE-2026-42295](https://insights.sbomify.com/CVE-2026-42295/): Argo Workflows: Exposure of artifact repository credentials (high 8.5) - [CVE-2026-42297](https://insights.sbomify.com/CVE-2026-42297/): Argo Workflows Is Missing Authorization in Sync ConfigMap Provider (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42294 and fix it if it is affected. What it is: CVE-2026-42294 is a high-severity denial of service vulnerability in argoproj argo-workflows, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42294 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - argo-workflows (Bitnami): affected all versions; fixed in 3.7.14, 4.0.5 - github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows/v2 (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-42294/ (Markdown: https://insights.sbomify.com/CVE-2026-42294/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42294 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42294 - OSV: https://osv.dev/vulnerability/CVE-2026-42294 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42294/ Summaries are generated and may contain mistakes; the official description above is the record.