<?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, 04 Oct 2026 11:56:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233521</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233521</link>
      <description>EUVD-2026-233521</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233521</guid>
    </item>
    <item>
      <title>fkie_cve-2022-39300</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39300</link>
      <description>&lt;p&gt;node SAML is a SAML 2.0 library based on the SAML implementation of passport-saml. A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. Users should upgrade to node-saml version 4.0.0-beta5 or newer. Disabling SAML authentication may be done as a workaround.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;node SAML is a SAML 2.0 library based on the SAML implementation of passport-saml. A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. Users should upgrade to node-saml version 4.0.0-beta5 or newer. Disabling SAML authentication may be done as a workaround.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-39300</guid>
    </item>
    <item>
      <title>GHSA-5p8w-2mvw-38pv — Signature bypass via multiple root elements</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5p8w-2mvw-38pv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-saml&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users should upgrade to node-saml v4.0.0-beta5 or newer.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable SAML authentication.&lt;/p&gt;
&lt;p&gt;### References
_Are there any links users can visit to find out more?_&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open a discussion in the [node-saml repo](https://github.com/node-saml/node-saml/discussions)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;* Felix Wilhelm of Google Project Zero&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-saml&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users should upgrade to node-saml v4.0.0-beta5 or newer.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable SAML authentication.&lt;/p&gt;
&lt;p&gt;### References
_Are there any links users can visit to find out more?_&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open a discussion in the [node-saml repo](https://github.com/node-saml/node-saml/discussions)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;* Felix Wilhelm of Google Project Zero&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5p8w-2mvw-38pv</guid>
    </item>
    <item>
      <title>gsd-2022-39300</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-39300</link>
      <description>gsd-2022-39300</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-39300</guid>
    </item>
  </channel>
</rss>
