CVE-2025-59531: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
High CVSS 7.5
- CVE id
- CVE-2025-59531
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Argo CD Runtimes and servers |
>= 1.2.0, <= 1.8.7 >= 2.0.0, < 2.14.20 >= 3.0.0, < 3.0.19 >= 3.1.0, < 3.1.8 |
2.14.20, 3.0.19, 3.1.8 |
How to fix it
Upgrade Argo CD to the fixed release of the line you run: 2.14.20, 3.0.19, 3.1.8.
- Upgrade Argo CD (the quay.io/argoproj/argocd image, or the argo-cd Helm chart) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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. Without a configured webhook.bitbucketserver.secret, Argo CD's /api/webhook endpoint crashes when receiving a malformed Bitbucket Server payload (non-array repository.links.clone field). A single unauthenticated request triggers CrashLoopBackOff, and targeting all replicas causes complete API outage. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.
References
- CVE-2025-59531 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-59531
- Web: https://github.com/argoproj/argo-cd/commit/5c466a4e39802e059e75c0008ae7b7b8e842538f
- Web: https://github.com/argoproj/argo-cd/security/advisories/GHSA-f9gq-prrc-hrhc
- Web: https://github.com/argoproj/argo-cd/security/advisories/GHSA-f9gq-prrc-hrhc
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.