<?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, 17 Nov 2026 08:50:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-221627</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221627</link>
      <description>EUVD-2026-221627</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221627</guid>
    </item>
    <item>
      <title>fkie_cve-2023-23627</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-23627</link>
      <description>&lt;p&gt;Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-23627</guid>
    </item>
    <item>
      <title>GHSA-fw3g-2h3j-qmm7 — Improper neutralization of `noscript` element content may allow XSS in Sanitize</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fw3g-2h3j-qmm7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sanitize&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize `&amp;gt;= 5.0.0, &amp;lt; 6.0.1` when Sanitize is configured with a custom allowlist that allows `noscript` elements. This could result in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.&lt;/p&gt;
&lt;p&gt;Sanitize&amp;#39;s default configs don&amp;#39;t allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Sanitize `&amp;gt;= 6.0.1` always removes `noscript` elements and their contents, even when `noscript` is in the allowlist.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The root cause of this issue is that HTML parsing rules treat the contents of a `noscript` element differently depending on whether scripting is enabled in the user agent. Nokogiri (the HTML parser Sanitize uses) doesn&amp;#39;t support scripting so it follows the &amp;#34;scripting disabled&amp;#34; rules, but a web browser with scripting enabled will follow the &amp;#34;scripting enabled&amp;#34; rules. This means that Sanitize can&amp;#39;t reliably make the contents of a `noscript` element safe for scripting enabled browsers. The safest thing to do is to remove the element and its contents entirely, which is now what Sanitize does in version 6.0.1 and later.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sanitize&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize `&amp;gt;= 5.0.0, &amp;lt; 6.0.1` when Sanitize is configured with a custom allowlist that allows `noscript` elements. This could result in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.&lt;/p&gt;
&lt;p&gt;Sanitize&amp;#39;s default configs don&amp;#39;t allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Sanitize `&amp;gt;= 6.0.1` always removes `noscript` elements and their contents, even when `noscript` is in the allowlist.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The root cause of this issue is that HTML parsing rules treat the contents of a `noscript` element differently depending on whether scripting is enabled in the user agent. Nokogiri (the HTML parser Sanitize uses) doesn&amp;#39;t support scripting so it follows the &amp;#34;scripting disabled&amp;#34; rules, but a web browser with scripting enabled will follow the &amp;#34;scripting enabled&amp;#34; rules. This means that Sanitize can&amp;#39;t reliably make the contents of a `noscript` element safe for scripting enabled browsers. The safest thing to do is to remove the element and its contents entirely, which is now what Sanitize does in version 6.0.1 and later.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fw3g-2h3j-qmm7</guid>
    </item>
    <item>
      <title>gsd-2023-23627</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-23627</link>
      <description>gsd-2023-23627</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-23627</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-23627</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-23627</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: ruby-sanitize, Ubuntu:22.04:LTS: ruby-sanitize&lt;/p&gt;
&lt;p&gt;Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: ruby-sanitize, Ubuntu:22.04:LTS: ruby-sanitize&lt;/p&gt;
&lt;p&gt;Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not allow `noscript` elements and are not vulnerable. This issue only affects users who are using a custom config that adds `noscript` to the element allowlist. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize&amp;#39;s default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-23627</guid>
    </item>
  </channel>
</rss>
