- Veröffentlicht
- 20.11.2026 04:59
- Zuletzt geändert
- 20.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
### Impact
The ApplicationSet cluster generator passes the annotations of each cluster Secret to the template as parameters. That included `kubectl.kubernetes.io/last-applied-configuration`, which `kubectl apply` (and Argo CD's default client-side apply) adds to an object and which holds the full applied manifest, including the Secret's `config` with the cluster's credentials. A user who can create or update an ApplicationSet could copy that annotation into a generated Application, for example into `spec.info`, and read the credentials of every cluster registered in Argo CD.
All versions from v2.4.0 onward are affected, up to the patched versions below. The cluster generator has exposed annotations since ApplicationSets were merged into Argo CD in [c77cf66aa](https://github.com/argoproj/argo-cd/commit/c77cf66aa1f7298216c91e9592f21bc5d924141c) ([#8864](https://github.com/argoproj/argo-cd/pull/8864)).
Only cluster Secrets created or updated with client-side `kubectl apply` carry the annotation; clusters added with `argocd cluster add` or through the API don't. The attacker needs permission to create or update ApplicationSets, for example through the ApplicationSet API or ApplicationSets in any namespace, and to read the generated Applications.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v3.6.0
* v3.5.7
* v3.4.13
* v3.3.19
The cluster generator no longer exposes `kubectl.kubernetes.io/last-applied-configuration` or Argo CD's own state annotations as parameters.
### Workarounds
* Remove the annotation from existing [cluster Secrets](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#clusters) with `kubectl annotate secret <name> -n argocd kubectl.kubernetes.io/last-applied-configuration-`, and manage them with [server-side apply](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#server-side-apply), which doesn't add it.
* Limit ApplicationSet create and update permissions to Argo CD admins using [RBAC](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/).
### Credits
This issue was found by the Argo CD team. Thanks to @gdsoumya for the fix.
### References
* Fix: [bc7becfbf](https://github.com/argoproj/argo-cd/commit/bc7becfbfdf0e8c166d9de826eb956751c0a717c) ([#30448](https://github.com/argoproj/argo-cd/pull/30448))
* Introducing commit: [c77cf66aa](https://github.com/argoproj/argo-cd/commit/c77cf66aa1f7298216c91e9592f21bc5d924141c) ([#8864](https://github.com/argoproj/argo-cd/pull/8864)), first released in v2.4.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/v2kein Fix bekanntGHSA-hr74-g9pw-j38m
Gogithub.com/argoproj/argo-cd/v33.3.19 || >= 3.4.0, 3.4.0 → 3.4.13 || >= 3.5.0, 3.5.0 → 3.5.7 || >= 3.6.0-rc1, 3.6.0GHSA-hr74-g9pw-j38m
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.