<?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>Mon, 05 Oct 2026 11:48:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-248637</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248637</link>
      <description>EUVD-2026-248637</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248637</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54419</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54419</link>
      <description>&lt;p&gt;A SAML library not dependent on any frameworks that runs in Node. In version 5.0.1, Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature. This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username. To conduct the attack an attacker would need a validly signed document from the identity provider (IdP). This is fixed in version 5.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A SAML library not dependent on any frameworks that runs in Node. In version 5.0.1, Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature. This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username. To conduct the attack an attacker would need a validly signed document from the identity provider (IdP). This is fixed in version 5.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54419</guid>
    </item>
    <item>
      <title>GHSA-4mxg-3p6v-xgq3 — Node-SAML SAML Signature Verification Vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4mxg-3p6v-xgq3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @node-saml/node-saml, npm: passport-saml, npm: @node-saml/passport-saml&lt;/p&gt;
&lt;p&gt;Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature.&lt;/p&gt;
&lt;p&gt;This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username.&lt;/p&gt;
&lt;p&gt;To conduct the attack an attacker would need a validly signed document from the identity provider (IdP).&lt;/p&gt;
&lt;p&gt;In fixing this we made sure to process the SAML assertions from only verified/authenticated contents. This will prevent future variants from coming up.&lt;/p&gt;
&lt;p&gt;Note: this is distinct from the previous xml-crypto CVEs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @node-saml/node-saml, npm: passport-saml, npm: @node-saml/passport-saml&lt;/p&gt;
&lt;p&gt;Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature.&lt;/p&gt;
&lt;p&gt;This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username.&lt;/p&gt;
&lt;p&gt;To conduct the attack an attacker would need a validly signed document from the identity provider (IdP).&lt;/p&gt;
&lt;p&gt;In fixing this we made sure to process the SAML assertions from only verified/authenticated contents. This will prevent future variants from coming up.&lt;/p&gt;
&lt;p&gt;Note: this is distinct from the previous xml-crypto CVEs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4mxg-3p6v-xgq3</guid>
    </item>
    <item>
      <title>RHSA-2025:14090 — Red Hat Security Advisory: Red Hat Developer Hub 1.7.0 release.</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:14090</link>
      <description>&lt;p&gt;rhdh: Red Hat Developer Hub user permissions pbkdf2: pbkdf2 silently returns predictable key material multer: Multer Denial of Service golang.org/x/net/proxy: golang.org/x/net/http/httpproxy: HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net http-proxy-middleware: Always-Incorrect Control Flow Implementation in http-proxy-middleware http-proxy-middleware: Improper Check for Unusual or Exceptional Conditions in http-proxy-middleware tar-fs: tar-fs has issue where extract can write outside the specified dir with a specific tarball multer: Multer vulnerable to Denial of Service via unhandled exception @node-saml/node-saml: Node-SAML Signature Verification Vulnerability&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rhdh: Red Hat Developer Hub user permissions pbkdf2: pbkdf2 silently returns predictable key material multer: Multer Denial of Service golang.org/x/net/proxy: golang.org/x/net/http/httpproxy: HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net http-proxy-middleware: Always-Incorrect Control Flow Implementation in http-proxy-middleware http-proxy-middleware: Improper Check for Unusual or Exceptional Conditions in http-proxy-middleware tar-fs: tar-fs has issue where extract can write outside the specified dir with a specific tarball multer: Multer vulnerable to Denial of Service via unhandled exception @node-saml/node-saml: Node-SAML Signature Verification Vulnerability&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:14090</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2664 — HCL BigFix: Schwachstelle ermöglicht Manipulation von Daten</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2664</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in HCL BigFix ausnutzen, um Daten zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in HCL BigFix ausnutzen, um Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2664</guid>
    </item>
  </channel>
</rss>
