<?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://vulnerability.circl.lu</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, 29 Sep 2026 23:50:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-16221 — fast-uri vulnerable to host confusion via literal backslash authority delimiter</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-16221</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fast-uri&lt;/p&gt;
&lt;p&gt;Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2) do not treat a literal backslash character (U+005C) as an authority delimiter. Node&amp;#39;s native WHATWG URL parser, used by fetch, undici, and Node&amp;#39;s http and https clients, normalizes the backslash to a forward slash for special schemes such as http, https, ws, wss, ftp, and file. As a result, the two parsers extract different hosts from the same input string. Applications that use fast-uri to enforce host-based policy such as allowlists, denylists, loopback or SSRF filtering, redirect validation, or outbound proxy routing before passing the same URL into Node&amp;#39;s URL or fetch consumers can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts.&lt;/p&gt;
&lt;p&gt;Patches: upgrade to fast-uri 4.1.1, 3.1.4, or 2.4.3.&lt;/p&gt;
&lt;p&gt;Workarounds: none.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fast-uri&lt;/p&gt;
&lt;p&gt;Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2) do not treat a literal backslash character (U+005C) as an authority delimiter. Node&amp;#39;s native WHATWG URL parser, used by fetch, undici, and Node&amp;#39;s http and https clients, normalizes the backslash to a forward slash for special schemes such as http, https, ws, wss, ftp, and file. As a result, the two parsers extract different hosts from the same input string. Applications that use fast-uri to enforce host-based policy such as allowlists, denylists, loopback or SSRF filtering, redirect validation, or outbound proxy routing before passing the same URL into Node&amp;#39;s URL or fetch consumers can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts.&lt;/p&gt;
&lt;p&gt;Patches: upgrade to fast-uri 4.1.1, 3.1.4, or 2.4.3.&lt;/p&gt;
&lt;p&gt;Workarounds: none.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-16221</guid>
    </item>
  </channel>
</rss>
