Servers and applications
GHSA-v9xr-fwqf-mgq4
Parameter override files can follow symlinks out of the repository
- Severity
- Medium 4.3
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Fixed in
- 2.0.0, 2.5.0
- Weakness
- Link following (CWE-59)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N- Sources
- Project advisories (GitHub)
Description
Parameter override files (.argocd-source.yaml and .argocd-source-.yaml) could be symlinks, and the repo-server read them without checking where the link pointed. Someone who can push to a repository used by an Application could link an override file to a YAML file elsewhere on the repo-server, for example in another repository's checkout. If that file's structure matched an Application source block, its values were merged into the Application's parameters and shown to anyone who can view the Application.
All versions from v1.8.0 onward are affected, up to the patched version below. Override files were introduced in c49dd8d38 (#4084).
The attacker needs push access to a repository used by an Application, and permission to view that Application. Only files that parse as an Application source block can be read.
Workarounds
Upgrade to v2.5.0 or later, and don't enable --allow-oob-symlinks. Before upgrading, limit push access to repositories that Applications use.
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
- 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-v9xr-fwqf-mgq4
- github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-v9xr-fwqf-mgq4