← Übersicht Argo CD

Parameter override files can follow symlinks out of the repository

GHSA-v9xr-fwqf-mgq4

Mittel · CVSS 4.3 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
20.11.2026 04:37
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact Parameter override files (`.argocd-source.yaml` and `.argocd-source-<app-name>.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](https://github.com/argoproj/argo-cd/commit/c49dd8d383a4f6653d2f806acbec8b41b73ed072) ([#4084](https://github.com/argoproj/argo-cd/pull/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. ### Patches A patch for this vulnerability has been released in the following Argo CD version: * v2.5.0 Since v2.5.0, the repo-server rejects any repository that contains a symlink pointing outside the repository before generating manifests, which includes override files. Installations that set `--allow-oob-symlinks` (`reposerver.allow.oob.symlinks`) turn this check off and are still affected. ### 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. ### Credits This issue was found by the Argo CD team. ### References * Fix: [179d1e0e8](https://github.com/argoproj/argo-cd/commit/179d1e0e8a8859e8cc865c2adc4a8038fca84299) ([#9843](https://github.com/argoproj/argo-cd/pull/9843), issue [#9738](https://github.com/argoproj/argo-cd/issues/9738)) * Introducing commit: [c49dd8d38](https://github.com/argoproj/argo-cd/commit/c49dd8d383a4f6653d2f806acbec8b41b73ed072) ([#4084](https://github.com/argoproj/argo-cd/pull/4084)), first released in v1.8.0 * [Store overrides in Git](https://argo-cd.readthedocs.io/en/stable/user-guide/parameters/#store-overrides-in-git) ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd1.8.0 → 2.0.0GHSA-v9xr-fwqf-mgq4
Gogithub.com/argoproj/argo-cd/v22.0.0 → 2.5.0GHSA-v9xr-fwqf-mgq4

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.