# CVE-2024-47827: Argo Workflows Controller: Denial of Service via malicious daemon Workflows > An attacker with workflow execution access can crash the Argo Workflows controller via a race condition, causing denial of service. - **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Oct 2024 - **Updated:** 4 Apr 2025 - **Also known as:** BIT-argo-workflows-2024-47827, GHSA-ghjw-32xw-ffwr, GO-2024-3226 ## What is CVE-2024-47827? CVE-2024-47827 is a medium-severity vulnerability in argoproj argo-workflows, published on 28 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Due to a race condition in a global variable in 3.6.0-rc1, the argo workflows controller can be made to crash on-command by any user with access to execute a workflow. This vulnerability is fixed in 3.6.0-rc2. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-1108 (Excessive Reliance on Global Variables) ## Which versions are affected by CVE-2024-47827? 6 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 | From 3.6.0-rc1 | 3.6.0-rc2 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.6.0-rc1 | 3.6.0-rc2 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.6.0-rc1 | 3.6.0-rc2 | | `argo-workflows` | Bitnami | From 3.6.0-rc1 | 3.6.0-rc2 | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v2` | Go | All versions | None | Products: Argoproj Argo Workflows. ## How do I fix CVE-2024-47827? Upgrade github.com/argoproj/argo-workflows/v3 to 3.6.0-rc2 or later. ## Is CVE-2024-47827 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47827 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-2024-47827 and fix it if it is affected. What it is: CVE-2024-47827 is a medium-severity vulnerability in argoproj argo-workflows, published on 28 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47827 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.6.0-rc1; fixed in 3.6.0-rc2 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.6.0-rc1; fixed in 3.6.0-rc2 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.6.0-rc1; fixed in 3.6.0-rc2 - argo-workflows (Bitnami): affected from 3.6.0-rc1; fixed in 3.6.0-rc2 - 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 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-2024-47827/ (Markdown: https://insights.sbomify.com/CVE-2024-47827/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47827 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47827 - OSV: https://osv.dev/vulnerability/CVE-2024-47827 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-47827/ Summaries are generated and may contain mistakes; the official description above is the record.