https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T18:37:02.412486+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2022-03973 bdu:2022-03973 2026-10-06T18:37:02.418588+00:00 bdu:2022-03973 https://cve.radiocsirt.org/vuln/euvd-2026-233965 EUVD-2026-233965 2026-10-06T18:37:02.418620+00:00 EUVD-2026-233965 https://cve.radiocsirt.org/vuln/fkie_cve-2022-31036 fkie_cve-2022-31036 2026-10-06T18:37:02.418633+00:00

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.

 https://cve.radiocsirt.org/vuln/ghsa-q4w5-4gq2-98vm GHSA-q4w5-4gq2-98vm — Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server 2026-10-06T18:37:02.418667+00:00

Affected: Go: github.com/argoproj/argo-cd, Go: github.com/argoproj/argo-cd/v2

### Impact

All unpatched versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server.

A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file.

Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server.

### Patches

A patch for this vulnerability has been released in the following Argo CD versions:

* v2.4.1 * v2.3.5 * v2.2.10 * v2.1.16

### Workarounds

* If you are using >=v2.3.0 and do not have any Helm-type Applications, [disable the Helm config management tool](https://argo-cd.readthedocs.io/en/stable/user-guide/tool_detection/#disable-built-in-tools).

#### Mitigations

* Avoid mounting YAML-formatted secrets as files on the repo-server. * Upgrade to >=2.3.0 to significantly reduce the risk of leaking out-of-bounds manifest files. Starting with 2.3.0, repository paths are randomized, and read permissions are restricted when manifests are not being actively being generated. This makes it very difficult to craft and use a malicious symlink.…

 https://cve.radiocsirt.org/vuln/gsd-2022-31036 gsd-2022-31036 2026-10-06T18:37:02.418718+00:00 gsd-2022-31036 https://cve.radiocsirt.org/vuln/rhsa-2022:5152 RHSA-2022:5152 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update 2026-10-06T18:37:02.418730+00:00

argocd: vulnerable to an uncontrolled memory consumption bug argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI. argocd: cross-site scripting (XSS) allow a malicious user to inject a javascript link in the UI argocd: vulnerable to a symlink following bug allowing a malicious user with repository write access