Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload

CVE-2025-59531GHSA-f9gq-prrc-hrhc

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-f9gq-prrc-hrhc 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-59531: 0.59% estimated exploitation activity in the next 30 days; percentile 48.16 (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.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 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. Observed crash (argocd-server restart): Mitigation If you use Bitbucket Server…

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

    Published from ghsa record GHSA-f9gq-prrc-hrhc

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-59531

Advisory: Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
IDs: CVE-2025-59531, GHSA-f9gq-prrc-hrhc
Record: https://patchnext.com/advisories/cve-2025-59531 (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-f9gq-prrc-hrhc (GitHub-reviewed advisory GHSA-f9gq-prrc-hrhc 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…