<?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>Tue, 06 Oct 2026 23:25:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343947</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343947</link>
      <description>EUVD-2026-343947</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343947</guid>
    </item>
    <item>
      <title>fkie_cve-2026-18089</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-18089</link>
      <description>&lt;p&gt;Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured.&lt;/p&gt;
&lt;p&gt;verify_xml in Net::SAML2::Role::VerifyXML runs &amp;#34;return if !$anchors &amp;amp;&amp;amp; !$cacert;&amp;#34; as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response&amp;#39;s own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with &amp;#34;return $xml unless $cacert;&amp;#34;.&lt;/p&gt;
&lt;p&gt;Any caller that constructs Binding::POST or calls Assertion-&amp;gt;new_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured.&lt;/p&gt;
&lt;p&gt;verify_xml in Net::SAML2::Role::VerifyXML runs &amp;#34;return if !$anchors &amp;amp;&amp;amp; !$cacert;&amp;#34; as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response&amp;#39;s own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with &amp;#34;return $xml unless $cacert;&amp;#34;.&lt;/p&gt;
&lt;p&gt;Any caller that constructs Binding::POST or calls Assertion-&amp;gt;new_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-18089</guid>
    </item>
    <item>
      <title>GHSA-p5j9-p2w8-q5rw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p5j9-p2w8-q5rw</link>
      <description>&lt;p&gt;Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured.&lt;/p&gt;
&lt;p&gt;verify_xml in Net::SAML2::Role::VerifyXML runs &amp;#34;return if !$anchors &amp;amp;&amp;amp; !$cacert;&amp;#34; as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response&amp;#39;s own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with &amp;#34;return $xml unless $cacert;&amp;#34;.&lt;/p&gt;
&lt;p&gt;Any caller that constructs Binding::POST or calls Assertion-&amp;gt;new_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured.&lt;/p&gt;
&lt;p&gt;verify_xml in Net::SAML2::Role::VerifyXML runs &amp;#34;return if !$anchors &amp;amp;&amp;amp; !$cacert;&amp;#34; as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response&amp;#39;s own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with &amp;#34;return $xml unless $cacert;&amp;#34;.&lt;/p&gt;
&lt;p&gt;Any caller that constructs Binding::POST or calls Assertion-&amp;gt;new_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p5j9-p2w8-q5rw</guid>
    </item>
  </channel>
</rss>
