Servers and applications
GHSA-94mc-2ch7-r5r5
A broken Helm repository entry stops Helm dependency builds for all projects
- Severity
- Medium 6.5
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Fixed in
- 2.0.0
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Sources
- Project advisories (GitHub)
Description
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 (#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.
Workarounds
Remove or fix the repository entry that breaks helm dependency build, and limit who can create repositories, including project-scoped repositories, using RBAC.
Affected software
| Software | Affected versions |
|---|---|
Argo CDServers and applications · github:argoproj/argo-cd |
|
About Argo CD
Declarative Continuous Deployment for Kubernetes
- Docker Hub pulls
- 149,231,128Docker Hub, 15 Nov 2026
- GitHub stars
- 24,612GitHub, 15 Nov 2026
- Forks
- 8,143GitHub, 15 Nov 2026
- Latest release
- v3.6.1GitHub, 15 Nov 2026
- Released
- 4 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 9 Feb 2018GitHub
Source code Website Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 3.6 | 3.6.1 | Yes |
| 3.5 | 3.5.7 | Yes |
| 3.4 | 3.4.13 | Yes |
| 3.3 | 3.3.19 | Ended 4 Nov 2026 |
| 3.2 | 3.2.12 | Ended 4 Aug 2026 |
| 3.1 | 3.1.16 | Ended 5 May 2026 |
From endoflife.date.
Vulnerabilities in Argo CD
- In our list
- 73
- Published in the last 12 months
- 18
- Critical, last 12 months
- 5
- High, last 12 months
- 8
- Known exploited
- 0
- GHSA-hr74-g9pw-j38mApplicationSet cluster generator exposes cluster credentials through the last-applied-configuration annotationHigh 7.7 20 Nov 2026
- GHSA-rq7v-q562-vwcqSymlinks in a tar archive allow writing files outside the extraction directoryHigh 8.5 20 Nov 2026
- GHSA-8f76-vwjj-hxgqApplicationSet SCM provider allowlist not enforced for Bitbucket Cloud and Azure DevOps pull request generatorsHigh 8.5 20 Nov 2026
- GHSA-h67h-99w8-xf8rUnauthenticated webhook request with an empty repository path crashes the API serverHigh 7.5 20 Nov 2026
- GHSA-9mrf-wvv5-62p9Unauthenticated pprof endpoints on the controller and API server metrics portsMedium 5.4 20 Nov 2026
- GHSA-v9xr-fwqf-mgq4Parameter override files can follow symlinks out of the repositoryMedium 4.3 20 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-94mc-2ch7-r5r5
- github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-94mc-2ch7-r5r5