- Veröffentlicht
- 20.11.2026 04:31
- Zuletzt geändert
- 20.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
### Impact
Before rendering a Helm chart that has dependencies, Argo CD added every Helm repository registered in Argo CD to the Helm configuration, not just the repositories the chart depends on. One broken repository entry was enough to make dependency builds fail for every Helm chart with dependencies, across all projects: for example, two repositories registered with the same name, or a repository whose `index.yaml` contains a non-semver version. A user who can register a Helm repository, including through a project-scoped repository, could use this to stop other teams' Helm applications from generating manifests and syncing.
All versions from v1.3.0 onward are affected, up to the patched versions below. The behavior dates from [4e9772e19](https://github.com/argoproj/argo-cd/commit/4e9772e19b8356e55a9cfe8f2ba5e4398e650f5b) ([#1865](https://github.com/argoproj/argo-cd/pull/1865)), which added Helm repository support.
Workloads that are already deployed keep running; affected Applications can't generate manifests or sync until the broken repository entry is removed.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.8.0
* v2.7.8
* v2.6.13
Argo CD now adds only the Helm repositories that the chart's dependencies reference.
### Workarounds
Remove or fix the repository entry that breaks `helm dependency build`, and limit who can create [repositories](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#repositories), including [project-scoped repositories](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#project-scoped-repositories-and-clusters), using [RBAC](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/).
### Credits
This issue was found by the Argo CD team.
### References
* Fix: [ea3a67a9f](https://github.com/argoproj/argo-cd/commit/ea3a67a9f36ecfdd76e45174c8ca5743a2069753); backports [#14528](https://github.com/argoproj/argo-cd/pull/14528) (2.7) and [#14529](https://github.com/argoproj/argo-cd/pull/14529) (2.6)
* Issue: [#14527](https://github.com/argoproj/argo-cd/issues/14527)
* Introducing commit: [4e9772e19](https://github.com/argoproj/argo-cd/commit/4e9772e19b8356e55a9cfe8f2ba5e4398e650f5b) ([#1865](https://github.com/argoproj/argo-cd/pull/1865)), first released in v1.3.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-cd1.3.0 → 2.0.0GHSA-94mc-2ch7-r5r5
Gogithub.com/argoproj/argo-cd/v22.6.13 || >= 2.7.0, 2.7.0 → 2.7.8GHSA-94mc-2ch7-r5r5
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.