All vulnerabilities

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
Weakness
Path traversal (CWE-22)Link following (CWE-59)
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.
From argoproj/argo-cd's security advisory. Shortened; the full text is there.

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.
Workarounds as given by argoproj/argo-cd's security advisory.

Affected software

SoftwareAffected versions
Argo CDServers and applications · github:argoproj/argo-cd
  • From 2.4.0 on

About Argo CD

Declarative Continuous Deployment for Kubernetes

From its GitHub repository.
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

Release lines

ReleaseLatestSecurity fixes
3.63.6.1Yes
3.53.5.7Yes
3.43.4.13Yes
3.33.3.19Ended 4 Nov 2026
3.23.2.12Ended 4 Aug 2026
3.13.1.16Ended 5 May 2026

From endoflife.date.

References