Servers and applications
GHSA-rq7v-q562-vwcq
Symlinks in a tar archive allow writing files outside the extraction directory
- Severity
- High 8.5
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L- Sources
- Project advisories (GitHub)
Description
When extracting a tar archive, Argo CD checked each entry's destination path by its text only, without resolving symlinks that earlier entries in the same archive had already created. An archive could create a symlink inside the destination, then a second symlink through it that pointed outside, and then a regular file through that chain. The file was then written to a location of the attacker's choice outside the extraction directory, and extraction reported success.
Two components extract archives supplied by the caller:
- repo-server, through the GetManifestsWithFiles API used for local diffs and syncs. Any user who can view an Application, which includes the built-in role:readonly, can send an archive. In a standard deployment the repo-server's writable locations are /tmp and its mounted volumes, where an attacker can tamper with other Applications' repository checkouts and cached charts.
- Config Management Plugin (CMP) sidecars, which receive archives from the repo-server.
Workarounds
- Restrict who can view Applications (applications, get) using RBAC. The built-in role:readonly grants it to every authenticated user by default.
- Run the repo-server and CMP sidecars with readOnlyRootFilesystem: true, which the default manifests set for the repo-server, so that the only writable locations are temporary volumes.
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-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-rq7v-q562-vwcq
- github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-rq7v-q562-vwcq