- Veröffentlicht
- 20.11.2026 04:47
- Zuletzt geändert
- 20.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
### Impact
With ApplicationSets in any namespace, users who aren't Argo CD admins can manage their own ApplicationSets, and the `--allowed-scm-providers` setting limits which SCM hosts their generators may contact. The Pull Request generator didn't apply that allowlist to Bitbucket Cloud or Azure DevOps. A user who can create or update an ApplicationSet could point one of those generators at a host they control and set `tokenRef` to any Secret in the Argo CD namespace. The ApplicationSet controller then sent that Secret's value to the attacker's host. The leaked Secret could be `argocd-secret`, whose token signing key lets the attacker mint an admin token.
All versions from v2.8.0 onward are affected, up to the patched version below. ApplicationSets in any namespace were introduced in [e8f512686](https://github.com/argoproj/argo-cd/commit/e8f512686e262691f8161141255725187c0558b4) ([#12378](https://github.com/argoproj/argo-cd/pull/12378)).
Only installations that enable ApplicationSets in any namespace and let users who aren't admins create or update ApplicationSets are affected. The attacker must run a host that can receive the request.
### Patches
A patch for this vulnerability has been released in the following Argo CD version:
* v2.10.0
The SCM provider allowlist now applies to every SCM and Pull Request generator, and SCM providers can be disabled entirely. Since v2.14.0, `tokenRef` can additionally be restricted to Secrets labeled `argocd.argoproj.io/secret-type: scm-creds` ([#20309](https://github.com/argoproj/argo-cd/pull/20309)).
### Workarounds
* Disable ApplicationSets in any namespace, or limit ApplicationSet create and update permissions, through every mechanism, to Argo CD admins.
* Restrict network egress from the ApplicationSet controller to trusted SCM hosts, including hosts inside the cluster.
* To limit the damage of a leaked signing key, disable the `admin` account and limit the permissions of local accounts and project roles.
See [SCM Providers secrets consideration](https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Appset-Any-Namespace/#scm-providers-secrets-consideration).
### Credits
This issue was found by the Argo CD team.
### References
* Fix: [43fe01a11](https://github.com/argoproj/argo-cd/commit/43fe01a113c35db31c3110c03d5f3be344a43ecb) ([#15248](https://github.com/argoproj/argo-cd/pull/15248))
* Additional hardening: [a25378f1e](https://github.com/argoproj/argo-cd/commit/a25378f1efcc09dc25a4169927e57bf2e15accca) ([#20309](https://github.com/argoproj/argo-cd/pull/20309))
* Introducing commit: [e8f512686](https://github.com/argoproj/argo-cd/commit/e8f512686e262691f8161141255725187c0558b4) ([#12378](https://github.com/argoproj/argo-cd/pull/12378)), first released in v2.8.0
### 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-cd/v22.8.0 → 2.10.0GHSA-8f76-vwjj-hxgq
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit 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.