Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload

CVE-2025-59537GHSA-wp4p-9pxh-cgx2

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

    Affected
    >= 2.0.0-rc1, <= 2.14.19
    Fixed in
    2.14.20

  • Go github.com/argoproj/argo-cd/v3

    Affected
    >= 3.2.0-rc1, <= 3.2.0-rc1>= 3.1.0-rc1, <= 3.1.7>= 3.0.0-rc1, <= 3.0.18
    Fixed in
    3.1.8, 3.0.19, 3.2.0-rc2

  • Go github.com/argoproj/argo-cd

    Affected
    >= 1.2.0, <= 1.8.7
    Fixed in
    no fixed version recorded

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-wp4p-9pxh-cgx2 lists affected ranges: Go github.com/argoproj/argo-cd >=1.2.0 =2.0.0-rc1 =3.2.0-rc1 =3.1.0-rc1 =3.0.0-rc1 <=3.0.18

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2025-59537: 0.60% estimated exploitation activity in the next 30 days; percentile 48.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-wp4p-9pxh-cgx2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59537

Advisory: argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload
IDs: CVE-2025-59537, GHSA-wp4p-9pxh-cgx2
Record: https://patchnext.com/advisories/cve-2025-59537 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v2 2.14.20; github.com/argoproj/argo-cd/v3 3.2.0-rc2, 3.1.8, 3.0.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.0.0-rc1, <= 2.14.19; fixed in 2.14.20
- Go github.com/argoproj/argo-cd/v3: affected >= 3.2.0-rc1, <= 3.2.0-rc1; >= 3.1.0-rc1, <= 3.1.7; >= 3.0.0-rc1, <= 3.0.18; fixed in 3.1.8, 3.0.19, 3.2.0-rc2
- Go github.com/argoproj/argo-cd: affected >= 1.2.0, <= 1.8.7

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd/v3: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3, github.com/argoproj/argo-cd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wp4p-9pxh-cgx2 (GitHub-reviewed advisory GHSA-wp4p-9pxh-cgx2 lists affected ranges: Go github.com/argoproj/argo-cd >=1.2.0 =2.0.0-rc1 =3.2.0-rc1 =3.1.0-rc1 =3.0.0-rc1 <=3.0.18)

Commands are suggestions: review each one before running it.

Loading voting…