<?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>Wed, 30 Sep 2026 07:58:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-7017 — HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-7017</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAARG HTTP::Tiny&lt;/p&gt;
&lt;p&gt;HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.&lt;/p&gt;
&lt;p&gt;When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller&amp;#39;s `headers` argument into the new request, without checking whether the redirect target shares an origin with the original URL. Caller-supplied `Authorization`, `Cookie` and `Proxy-Authorization` headers are therefore re-sent to whatever host the redirect names, across scheme, host or port boundaries, and including `https` to `http` downgrades that expose them in plaintext on the wire.&lt;/p&gt;
&lt;p&gt;The HTTP::Tiny POD note that &amp;#34;Authorization headers will not be included in a redirected request&amp;#34; applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAARG HTTP::Tiny&lt;/p&gt;
&lt;p&gt;HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.&lt;/p&gt;
&lt;p&gt;When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller&amp;#39;s `headers` argument into the new request, without checking whether the redirect target shares an origin with the original URL. Caller-supplied `Authorization`, `Cookie` and `Proxy-Authorization` headers are therefore re-sent to whatever host the redirect names, across scheme, host or port boundaries, and including `https` to `http` downgrades that expose them in plaintext on the wire.&lt;/p&gt;
&lt;p&gt;The HTTP::Tiny POD note that &amp;#34;Authorization headers will not be included in a redirected request&amp;#34; applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-7017</guid>
    </item>
  </channel>
</rss>
