<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T15:51:14.584380+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-234124</id>
    <title>EUVD-2026-234124</title>
    <updated>2026-10-08T15:51:14.590256+00:00</updated>
    <content>EUVD-2026-234124</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-234124"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-24904</id>
    <title>fkie_cve-2022-24904</title>
    <updated>2026-10-08T15:51:14.590290+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 0.7.0 and prior to versions 2.1.15m 2.2.9, and 2.3.4 is vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive 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 directory-type Application may commit a symlink which points to an out-of-bounds 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 JSON-formatted secrets which have been mounted as files on the repo-server. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. Users of versions 2.3.0 or above who do not have any Jsonnet/directory-type Applications may disable the Jsonnet/directory config management tool as a workaround.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-24904"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6gcg-hp2x-q54h</id>
    <title>GHSA-6gcg-hp2x-q54h — Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server</title>
    <updated>2026-10-08T15:51:14.590327+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/argoproj/argo-cd/v2</p>
<p>### Impact</p>
<p>All unpatched versions of Argo CD starting with v0.7.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive files from Argo CD's repo-server.</p>
<p>A malicious Argo CD user with write access for a repository which is (or may be) used in a directory-type Application may commit a symlink which points to an out-of-bounds file. 
* If the target file is a valid JSON or YAML manifest file, and the resource is allowed in the Application, the attacker can read the contents of that manifest file. (In versions &lt;2.3.2, &lt;2.2.8, and &lt;2.1.14, the attacker may read the files contents even if the resource is _not_ allowed in the Application). 
* If the target file is valid JSON but is _not_ a manifest file, the attacker may read the contents of the file. 
* If the target file is not valid JSON or YAML, the attacker may read partial file contents (usually just the first character of the file).</p>
<p>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 JSON-formatted secrets which have been mounted as files on the repo-server.</p>
<p>### Patches</p>
<p>A patch for this vulnerability has been released in the following Argo CD versions:</p>
<p>* v2.3.4
* v2.2.9
* v2.1.15</p>
<p>### Workarounds</p>
<p>* If you are using &gt;=v2.3.0 and do not have any Jsonnet/directory-type Applications, [disable the Jsonnet/directory config management too…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6gcg-hp2x-q54h"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-24904</id>
    <title>gsd-2022-24904</title>
    <updated>2026-10-08T15:51:14.590380+00:00</updated>
    <content>gsd-2022-24904</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-24904"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2022:4671</id>
    <title>RHSA-2022:4671 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update</title>
    <updated>2026-10-08T15:51:14.590393+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>argocd: Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server argocd: Login screen allows message spoofing if SSO is enabled argocd: ArgoCD will blindly trust JWT claims if anonymous access is enabled</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2022:4671"/>
  </entry>
</feed>
