Servers and applications
GHSA-8f76-vwjj-hxgq
ApplicationSet SCM provider allowlist not enforced for Bitbucket Cloud and Azure DevOps pull request generators
- Severity
- High 8.5
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Fixed in
- 2.10.0
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H- Sources
- Project advisories (GitHub)
Description
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 (#12378).
Only installations that enable ApplicationSets in any namespace and let users who aren't admins create or update ApplicationSets are affected.
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.
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-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
- CVE-2021-26922Logging out does not revoke local user session tokens, which never expireHigh 7.4 20 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-8f76-vwjj-hxgq
- github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-8f76-vwjj-hxgq