# CVE-2025-59537: argo-cd is vulnerable to unauthenticated DoS attack via malformed Gogs webhook payload > Unauthenticated attackers can crash the Argo CD API server by sending malformed Gogs webhook payloads, causing 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-59537, CLEANSTART-2026-ZP55576, GHSA-wp4p-9pxh-cgx2, GO-2025-3996, MINI-26hr-jvp8-jprw, MINI-84jr-wvg3-5xfx, MINI-853j-q2v3-9wg4, MINI-9hhg-68gr-pc9v, MINI-fxjc-q33j-rrfv, MINI-gwgq-ww8q-j256, MINI-j7jx-gqr8-93qm, MINI-mv34-p8r4-hxxv, MINI-qprx-cxwc-697f, MINI-v8xm-4m9q-9p75 ## What is CVE-2025-59537? CVE-2025-59537 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. Versions 1.2.0 through 1.8.7, 2.0.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.7 and 3.0.18 are vulnerable to malicious API requests which can crash the API server and cause denial of service to legitimate clients. With the default configuration, no webhook.gogs.secret set, Argo CD’s /api/webhook endpoint will crash the entire argocd-server process when it receives a Gogs push event whose JSON field commits[].repo is not set or is null. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19. Weakness: CWE-476 (NULL Pointer Dereference), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2025-59537? 14 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 1.2.0 | 2.14.20, 3.0.19, 3.1.8 | | `github.com/argoproj/argo-cd` | Go | From 1.2.0 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0 to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0 to 1.8.7 | None | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.14.20 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc1 | 2.14.20 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc1 | 2.14.20 | Products: Argoproj Argo Cd. ## How do I fix CVE-2025-59537? 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-59537 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59537 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-59537 and fix it if it is affected. What it is: CVE-2025-59537 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-59537 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 1.2.0; fixed in 2.14.20, 3.0.19, 3.1.8 - github.com/argoproj/argo-cd (Go): affected from 1.2.0; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd/v2 (Go): affected all versions; 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-59537/ (Markdown: https://insights.sbomify.com/CVE-2025-59537/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59537 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59537 - OSV: https://osv.dev/vulnerability/CVE-2025-59537 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59537/ Summaries are generated and may contain mistakes; the official description above is the record.