<?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:59:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-4054 — Cross-site Scripting in Sanitize</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-4054</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rgrove Sanitize&lt;/p&gt;
&lt;p&gt;In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less than 5.2.1, there is a cross-site scripting vulnerability. When HTML is sanitized using Sanitize&amp;#39;s &amp;#34;relaxed&amp;#34; config, or a custom config that allows certain elements, some content in a math or svg element may not be sanitized correctly even if math and svg are not in the allowlist. You are likely to be vulnerable to this issue if you use Sanitize&amp;#39;s relaxed config or a custom config that allows one or more of the following HTML elements: iframe, math, noembed, noframes, noscript, plaintext, script, style, svg, xmp. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. This has been fixed in 5.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rgrove Sanitize&lt;/p&gt;
&lt;p&gt;In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less than 5.2.1, there is a cross-site scripting vulnerability. When HTML is sanitized using Sanitize&amp;#39;s &amp;#34;relaxed&amp;#34; config, or a custom config that allows certain elements, some content in a math or svg element may not be sanitized correctly even if math and svg are not in the allowlist. You are likely to be vulnerable to this issue if you use Sanitize&amp;#39;s relaxed config or a custom config that allows one or more of the following HTML elements: iframe, math, noembed, noframes, noscript, plaintext, script, style, svg, xmp. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. This has been fixed in 5.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-4054</guid>
    </item>
    <item>
      <title>GHSA-p4x4-rw2p-8j8m — Cross-site Scripting in Sanitize</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p4x4-rw2p-8j8m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sanitize&lt;/p&gt;
&lt;p&gt;When HTML is sanitized using Sanitize&amp;#39;s &amp;#34;relaxed&amp;#34; config or a custom config that allows certain elements, some content in a `&amp;lt;math&amp;gt;` or `&amp;lt;svg&amp;gt;` element may not be sanitized correctly even if `math` and `svg` are not in the allowlist.&lt;/p&gt;
&lt;p&gt;You are likely to be vulnerable to this issue if you use Sanitize&amp;#39;s relaxed config or a custom config that allows one or more of the following HTML elements:&lt;/p&gt;
&lt;p&gt;- `iframe`
- `math`
- `noembed`
- `noframes`
- `noscript`
- `plaintext`
- `script`
- `style`
- `svg`
- `xmp`&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, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.&lt;/p&gt;
&lt;p&gt;### Releases&lt;/p&gt;
&lt;p&gt;This problem has been fixed in Sanitize 5.2.1.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not possible, a workaround is to override the default value of Sanitize&amp;#39;s `:remove_contents` config option with the following value, which ensures that the contents of `math` and `svg` elements (among others) are removed entirely when those elements are not in the allowlist:&lt;/p&gt;
&lt;p&gt;```ruby
%w[iframe math noembed noframes noscript plaintext script style svg xmp]
```&lt;/p&gt;
&lt;p&gt;For example, if you currently use Sanitize&amp;#39;s relaxed config, you can create a custom config object that overrides the default value of `:remove_contents` like this:&lt;/p&gt;
&lt;p&gt;```ruby
custom_config = Sanitize::Config.merge(
  Sanitize::Config::RELAXED,
  :remove_contents =&amp;gt; %w[iframe math noembed noframes noscript…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sanitize&lt;/p&gt;
&lt;p&gt;When HTML is sanitized using Sanitize&amp;#39;s &amp;#34;relaxed&amp;#34; config or a custom config that allows certain elements, some content in a `&amp;lt;math&amp;gt;` or `&amp;lt;svg&amp;gt;` element may not be sanitized correctly even if `math` and `svg` are not in the allowlist.&lt;/p&gt;
&lt;p&gt;You are likely to be vulnerable to this issue if you use Sanitize&amp;#39;s relaxed config or a custom config that allows one or more of the following HTML elements:&lt;/p&gt;
&lt;p&gt;- `iframe`
- `math`
- `noembed`
- `noframes`
- `noscript`
- `plaintext`
- `script`
- `style`
- `svg`
- `xmp`&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, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.&lt;/p&gt;
&lt;p&gt;### Releases&lt;/p&gt;
&lt;p&gt;This problem has been fixed in Sanitize 5.2.1.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not possible, a workaround is to override the default value of Sanitize&amp;#39;s `:remove_contents` config option with the following value, which ensures that the contents of `math` and `svg` elements (among others) are removed entirely when those elements are not in the allowlist:&lt;/p&gt;
&lt;p&gt;```ruby
%w[iframe math noembed noframes noscript plaintext script style svg xmp]
```&lt;/p&gt;
&lt;p&gt;For example, if you currently use Sanitize&amp;#39;s relaxed config, you can create a custom config object that overrides the default value of `:remove_contents` like this:&lt;/p&gt;
&lt;p&gt;```ruby
custom_config = Sanitize::Config.merge(
  Sanitize::Config::RELAXED,
  :remove_contents =&amp;gt; %w[iframe math noembed noframes noscript…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p4x4-rw2p-8j8m</guid>
    </item>
  </channel>
</rss>
