dbcve.org
Argo CdApplication · Argoproj

CVE-2025-59531

HIGH · 7.5 CVSS v3.1 Published 2025-10-01
Fix available
A fix is available. Upgrade to 2.14.20 / 3.0.19 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Argo CdApplication
Affected:>= 1.2.0, <= 1.8.7>= 2.0.0, < 2.14.20>= 3.0.0, < 3.0.19>= 3.1.0, < 3.1.8= 3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.14.20 / 3.0.19 / 3.1.8 or later
Fixed in 2.14.203.0.193.1.8
Vendor patch github.com →
Recommended fix High confidence

2.14.20 (for 2.x), 3.0.19 (for 3.0.x), 3.1.8 (for 3.1.x), or 3.2.0-rc2+ (for 3.2.x)

  1. Identify your current Argo CD version using 'argocd version' or checking the deployment
  2. Upgrade to version 2.14.20 or later if running 2.x, upgrade to 3.0.19 or later if running 3.0.x, upgrade to 3.1.8 or later if running 3.1.x, or upgrade to 3.2.0-rc2 or later if running 3.2.x
  3. For Kubernetes deployments, update the Argo CD image tag in your manifests or Helm values to the fixed version
  4. Apply the upgrade using 'kubectl apply -f' or your GitOps workflow
  5. Verify the upgrade succeeded by checking pod status with 'kubectl get pods -n argocd' and confirming the API server is responding
  6. As an additional config mitigation, configure webhook.bitbucketserver.secret in argocd-cm ConfigMap to prevent similar issues
Caveat Minor version upgrades within the same major series should be low-risk; always review release notes for breaking changes before upgrading across major versions

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59531 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data