# CVE-2025-59538: Argo CD is Vulnerable to Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook > Unauthenticated attackers can crash the Argo CD server by sending a malformed Azure DevOps webhook payload, causing a denial of service. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Oct 2025 - **Updated:** 2 Oct 2025 - **Also known as:** BIT-argo-cd-2025-59538, CLEANSTART-2026-KN43906, GHSA-gpx4-37g2-c8pv, GO-2025-3995, MINI-5753-2gwx-fx73, MINI-5gv4-hjcp-rv89, MINI-5qjc-cm2c-w556, MINI-849m-6v57-5pfm, MINI-c56q-9h2g-vwp7, MINI-cvx4-fwf6-hx4q, MINI-j56v-5w64-jj94, MINI-ph42-wxmm-956h, MINI-v686-9v2v-cqh9, MINI-v6v3-6m8m-jxw4 ## What is CVE-2025-59538? CVE-2025-59538 is a high-severity denial of service vulnerability in Argoproj Argo Cd, published on 1 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. For versions 2.9.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.6 and 3.0.17, when the webhook.azuredevops.username and webhook.azuredevops.password are not set in the default configuration, the /api/webhook endpoint crashes the entire argocd-server process when it receives an Azure DevOps Push event whose JSON array resource.refUpdates is empty. The slice index [0] is accessed without a length check, causing an index-out-of-range panic. A single unauthenticated HTTP POST is enough to kill the process. This issue is resolved in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19. Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions), CWE-248 (Uncaught Exception) ## Which versions are affected by CVE-2025-59538? 12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v3, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0-rc1 | 3.0.19, 3.1.8, 3.2.0-rc2 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0-rc1 | 3.0.19 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0-rc1 | 3.0.19 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.1.0-rc1 | 3.1.8 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.1.0-rc1 | 3.1.8 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.2.0-rc1 | 3.2.0-rc2 | | `github.com/argoproj/argo-cd/v3` | Go | From 3.2.0-rc1 | 3.2.0-rc2 | | `argo-cd` | Bitnami | From 2.9.0 | 2.14.20, 3.0.19, 3.1.8 | | `github.com/argoproj/argo-cd` | Go | All versions | None | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.14.20 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.14.20 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.14.20 | Products: Argoproj Argo Cd. ## How do I fix CVE-2025-59538? Upgrade github.com/argoproj/argo-cd/v3 to a fixed version for your release line: 3.0.19, 3.1.8 or 3.2.0-rc2. ## Is CVE-2025-59538 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59538 exists. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-59538 and fix it if it is affected. What it is: CVE-2025-59538 is a high-severity denial of service vulnerability in Argoproj Argo Cd, published on 1 Oct 2025. 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-2025-59538 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0-rc1; fixed in 3.0.19, 3.1.8, 3.2.0-rc2 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0-rc1; fixed in 3.0.19 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0-rc1; fixed in 3.0.19 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.1.0-rc1; fixed in 3.1.8 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.1.0-rc1; fixed in 3.1.8 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.2.0-rc1; fixed in 3.2.0-rc2 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.2.0-rc1; fixed in 3.2.0-rc2 - argo-cd (Bitnami): affected from 2.9.0; fixed in 2.14.20, 3.0.19, 3.1.8 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.14.20 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.14.20 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.14.20 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-2025-59538/ (Markdown: https://insights.sbomify.com/CVE-2025-59538/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59538 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59538 - OSV: https://osv.dev/vulnerability/CVE-2025-59538 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59538/ Summaries are generated and may contain mistakes; the official description above is the record.