<?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, 12 Oct 2026 17:35:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-73492 — Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-73492</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flavorjones loofah&lt;/p&gt;
&lt;p&gt;Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as &amp;amp;#58, &amp;amp;#9, &amp;amp;#10, or &amp;amp;#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah&amp;#39;s default sanitize() path is not affected. This issue is fixed in version 2.25.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flavorjones loofah&lt;/p&gt;
&lt;p&gt;Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as &amp;amp;#58, &amp;amp;#9, &amp;amp;#10, or &amp;amp;#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah&amp;#39;s default sanitize() path is not affected. This issue is fixed in version 2.25.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-73492</guid>
    </item>
  </channel>
</rss>
