<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 18 Oct 2026 01:05:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-185345</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-185345</link>
      <description>EUVD-2026-185345</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-185345</guid>
    </item>
    <item>
      <title>fkie_cve-2021-23347</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-23347</link>
      <description>&lt;p&gt;The package github.com/argoproj/argo-cd/cmd before 1.7.13, from 1.8.0 and before 1.8.6 are vulnerable to Cross-site Scripting (XSS) the SSO provider connected to Argo CD would have to send back a malicious error message containing JavaScript to the user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The package github.com/argoproj/argo-cd/cmd before 1.7.13, from 1.8.0 and before 1.8.6 are vulnerable to Cross-site Scripting (XSS) the SSO provider connected to Argo CD would have to send back a malicious error message containing JavaScript to the user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-23347</guid>
    </item>
    <item>
      <title>GHSA-qq5v-f4c3-395c — Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd/v2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qq5v-f4c3-395c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-cd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When using SSO with the Argo CD CLI, a malicious SSO provider could have sent specially crafted error message that would result in XSS on the client by means of executing arbitrary JavaScript code.&lt;/p&gt;
&lt;p&gt;We believe the exploitation of this vulnerability is only be possible when Argo CD is connected to a compromised/malicious SSO provider.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;* Do not use SSO with the CLI when you don&amp;#39;t trust your SSO provider&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* 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`&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;The issue was found during static code scanning with CodeQL and fixed by the Argo CD team. While we believed that a rogue SSO provider would pose a severe threat by itself, we fixed it like a regular bug.&lt;/p&gt;
&lt;p&gt;The Argo CD team would like to thank Adam Gold of Snyk (https://snyk.io) for stepping up and classifying this correctly as a  security issue and for his help in determining its severity. Also, Snyk kindly reserved and provided the CVE for this vulnerability.&lt;/p&gt;
&lt;p&gt;We fully agree with Adam that this bug is a security vulnerability and justifies publishing a SA, to provide our community and users full transparancy.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-cd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When using SSO with the Argo CD CLI, a malicious SSO provider could have sent specially crafted error message that would result in XSS on the client by means of executing arbitrary JavaScript code.&lt;/p&gt;
&lt;p&gt;We believe the exploitation of this vulnerability is only be possible when Argo CD is connected to a compromised/malicious SSO provider.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;* Do not use SSO with the CLI when you don&amp;#39;t trust your SSO provider&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* 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`&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;The issue was found during static code scanning with CodeQL and fixed by the Argo CD team. While we believed that a rogue SSO provider would pose a severe threat by itself, we fixed it like a regular bug.&lt;/p&gt;
&lt;p&gt;The Argo CD team would like to thank Adam Gold of Snyk (https://snyk.io) for stepping up and classifying this correctly as a  security issue and for his help in determining its severity. Also, Snyk kindly reserved and provided the CVE for this vulnerability.&lt;/p&gt;
&lt;p&gt;We fully agree with Adam that this bug is a security vulnerability and justifies publishing a SA, to provide our community and users full transparancy.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qq5v-f4c3-395c</guid>
    </item>
    <item>
      <title>gsd-2021-23347</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-23347</link>
      <description>gsd-2021-23347</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-23347</guid>
    </item>
  </channel>
</rss>
