Servers and applications
GHSA-hr74-g9pw-j38m
ApplicationSet cluster generator exposes cluster credentials through the last-applied-configuration annotation
- Severity
- High 7.7
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Weakness
- Information exposure (CWE-200)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
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 (#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.
Workarounds
- Remove the annotation from existing cluster Secrets with kubectl annotate secret -n argocd kubectl.kubernetes.io/last-applied-configuration-, and manage them with server-side apply, which doesn't add it.
- Limit ApplicationSet create and update permissions to Argo CD admins 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-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
- 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-hr74-g9pw-j38m
- github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-hr74-g9pw-j38m