← Übersicht Argo CD

Unauthenticated webhook request with an empty repository path crashes the API server

GHSA-h67h-99w8-xf8r

Hoch · CVSS 7.5 Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
20.11.2026 04:41
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact A webhook push event whose repository URL has no path, such as `http://my.domain.com`, made the API server index past the end of an empty string while matching the event to Applications. The resulting panic happened in a webhook worker goroutine, outside any request recovery, so the whole `argocd-server` process crashed. `/api/webhook` doesn't use Argo CD authentication and is usually reachable from the internet, so anyone could crash the API server repeatedly with a single unauthenticated request. All versions from v0.4.0 onward are affected, up to the patched version below. The unchecked index was introduced with webhook support in [ac938fe8a](https://github.com/argoproj/argo-cd/commit/ac938fe8a3af46f7aac07d607bfdd0a375e74103) ([#160](https://github.com/argoproj/argo-cd/pull/160)). A webhook secret for the provider used in the request blocks this, but providers without a configured secret accept unsigned events, so in practice most installations were exposed. ### Patches A patch for this vulnerability has been released in the following Argo CD version: * v3.1.0 The fix was not backported; Argo CD 3.0 and earlier are out of support. ### Workarounds Configure a [webhook secret](https://argo-cd.readthedocs.io/en/stable/operator-manual/webhook/) for every Git provider, or block access to `/api/webhook` at your ingress or load balancer if you don't use webhooks. ### Credits The Argo CD team would like to thank @regiontog for responsibly disclosing this issue. ### References * Fix: [3e7625a25](https://github.com/argoproj/argo-cd/commit/3e7625a255807d0207d8ac50cba5d94c975b84a4) ([#23042](https://github.com/argoproj/argo-cd/pull/23042)) * Introducing commit: [ac938fe8a](https://github.com/argoproj/argo-cd/commit/ac938fe8a3af46f7aac07d607bfdd0a375e74103) ([#160](https://github.com/argoproj/argo-cd/pull/160)), first released in v0.4.0 * [Webhook configuration](https://argo-cd.readthedocs.io/en/stable/operator-manual/webhook/) ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd0.4.0 → 2.0.0GHSA-h67h-99w8-xf8r
Gogithub.com/argoproj/argo-cd/v2kein Fix bekanntGHSA-h67h-99w8-xf8r
Gogithub.com/argoproj/argo-cd/v33.0.0 → 3.1.0GHSA-h67h-99w8-xf8r

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.