<?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-10-03T21:45:23.052537+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/brew-perl-build-cve-2026-7017</id>
    <title>BREW-perl-build-CVE-2026-7017 — HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets</title>
    <updated>2026-10-03T21:45:23.056907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: perl-build</p>
<p>HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.</p>
<p>When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller'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.</p>
<p>The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-perl-build-cve-2026-7017"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-7017</id>
    <title>fkie_cve-2026-7017</title>
    <updated>2026-10-03T21:45:23.065095+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.</p>
<p>When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller'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.</p>
<p>The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-7017"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-pgc4-5jjm-7rr7</id>
    <title>GHSA-pgc4-5jjm-7rr7</title>
    <updated>2026-10-03T21:45:23.065211+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.</p>
<p>When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller'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.</p>
<p>The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-pgc4-5jjm-7rr7"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/oesa-2026-3169</id>
    <title>OESA-2026-3169 — perl-HTTP-Tiny security update</title>
    <updated>2026-10-03T21:45:23.065257+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: perl-HTTP-Tiny, openEuler:24.03-LTS-SP1: perl-HTTP-Tiny, openEuler:24.03-LTS-SP3: perl-HTTP-Tiny, openEuler:24.03-LTS-SP4: perl-HTTP-Tiny, openEuler:20.03-LTS-SP4: perl-HTTP-Tiny</p>
<p>This is a very simple HTTP/1.1 client, designed for doing simple requests  without the overhead of a large framework like LWP::UserAgent.

Security Fix(es):</p>
<p>HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.</p>
<p>When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller&amp;apos;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.</p>
<p>The HTTP::Tiny POD note that &amp;quot;Authorization headers will not be included in a redirected request&amp;quot; applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.(CVE-2026-7017)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/oesa-2026-3169"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11219-1</id>
    <title>openSUSE-SU-2026:11219-1 — perl-HTTP-Tiny-0.096-2.1 on GA media</title>
    <updated>2026-10-03T21:45:23.065340+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>perl-HTTP-Tiny-0.096-2.1 on GA media</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/opensuse-su-2026:11219-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-7017</id>
    <title>UBUNTU-CVE-2026-7017</title>
    <updated>2026-10-03T21:45:23.065387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: perl, Ubuntu:Pro:16.04:LTS: perl, Ubuntu:16.04:LTS: libhttp-tiny-perl, Ubuntu:Pro:18.04:LTS: perl, Ubuntu:18.04:LTS: libhttp-tiny-perl, Ubuntu:Pro:20.04:LTS: perl, Ubuntu:20.04:LTS: libhttp-tiny-perl, Ubuntu:22.04:LTS: libhttp-tiny-perl, Ubuntu:22.04:LTS: perl, Ubuntu:24.04:LTS: libhttp-tiny-perl and 5 more</p>
<p>HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets. When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller'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. The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-7017"/>
  </entry>
</feed>
