<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T02:49:23.438463+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-v39h-62p7-jpjc</id>
    <title>GHSA-v39h-62p7-jpjc — fast-uri vulnerable to host confusion via percent-encoded authority delimiters</title>
    <updated>2026-09-29T02:49:23.439596+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: fast-uri</p>
<p>### Impact</p>
<p>`fast-uri` v3.1.1 and earlier decodes percent-encoded authority delimiters (`%40` as `@`, `%3A` as `:`) inside the host component and serializes them back as raw characters. This changes the URI structure, turning a hostname into userinfo plus a different host.</p>
<p>For example, `http://trusted.com%40evil.com/` normalizes to `http://trusted.com@evil.com/`, which reparses as host `evil.com` with userinfo `trusted.com`.</p>
<p>Applications that normalize untrusted URLs before host allowlist checks, redirect validation, or outbound request routing can be steered to a different authority than the original URL appeared to contain.</p>
<p>### Patches</p>
<p>Upgrade to `fast-uri` &gt;= 3.1.2, or if you are in the v2.x release line, v2.4.1</p>
<p>### Workarounds</p>
<p>None. Upgrade to the patched version.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-v39h-62p7-jpjc"/>
  </entry>
</feed>
