argo-cd is vulnerable to unauthenticated DoS attack via malformed Gogs webhook payload

Summary

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.

Timeline

1. Oct 1, 2025, 9:01 PM UTCCVE published
2. Oct 2, 2025, 3:35 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: yes · Technical impact: partial

3. Oct 2, 2025, 3:54 PM UTCRecord last updated

Affected versions

• argoproj argo-cd

  From 1.2.0 · through 1.8.7; From 2.0.0-rc1 · fixed in 2.14.20; From 3.2.0-rc1 · fixed in 3.2.0-rc2; From 3.1.0-rc1 · fixed in 3.1.8; From 3.0.0-rc1 · fixed in 3.0.19

• github.com/argoproj/argo-cdGo

  From 1.2.0 · through 1.8.7

• github.com/argoproj/argo-cd/v2Go

  From 2.0.0-rc1 · fixed in 2.14.20

• github.com/argoproj/argo-cd/v3Go

  From 3.2.0-rc1 · fixed in 3.2.0-rc2

• github.com/argoproj/argo-cd/v3Go

  From 3.1.0-rc1 · fixed in 3.1.8

• github.com/argoproj/argo-cd/v3Go

  From 3.0.0-rc1 · fixed in 3.0.19

• github.com/argoproj/argo-cdGo

  From 1.2.0

• github.com/argoproj/argo-cd/v2Go

  fixed in 2.14.20

• github.com/argoproj/argo-cd/v3Go

  From 3.0.0-rc1 · fixed in 3.0.19; From 3.1.0-rc1 · fixed in 3.1.8; From 3.2.0-rc1 · fixed in 3.2.0-rc2

References 2