<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T07:47:30.299858+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/cve-2026-5773</id>
    <title>CVE-2026-5773 — wrong reuse of SMB connection</title>
    <updated>2026-11-21T07:47:30.301236+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> curl</p>
<p>libcurl might in some circumstances reuse the wrong connection for SMB(S)
transfers.</p>
<p>libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.</p>
<p>When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a network transfer operation that was requested by an
application could wrongfully reuse an existing SMB connection to the same
server that was using a different "share" than the new subsequent transfer
should.</p>
<p>This could in unlucky situations lead to the download of the wrong file or the
upload of a file to the wrong place. When this happens, the same credentials
are used and the server name is the same.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-5773"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-8227-1</id>
    <title>USN-8227-1 — curl vulnerabilities</title>
    <updated>2026-11-21T07:47:30.301288+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl</p>
<p>It was discovered that curl incorrectly reused non-TLS connections when
TLS was required in some STARTTLS configurations. A remote attacker could
possibly use this issue to obtain sensitive information. (CVE-2026-4873)</p>
<p>It was discovered that curl incorrectly reused certain HTTP Negotiate
connections. A remote attacker could possibly use this issue to obtain
sensitive information. (CVE-2026-5545)</p>
<p>It was discovered that curl incorrectly reused certain SMB connections. A
remote attacker could possibly use this issue to obtain sensitive
information. (CVE-2026-5773)</p>
<p>It was discovered that curl could leak proxy credentials when handling
redirects in some configurations. A remote attacker could possibly use
this issue to obtain sensitive information. (CVE-2026-6253)</p>
<p>It was discovered that curl could leak cookies because of stale custom
cookie host handling in some requests. A remote attacker could possibly
use this issue to obtain sensitive information. (CVE-2026-6276)</p>
<p>It was discovered that curl could leak .netrc credentials when reusing
proxy connections in some situations. A remote attacker could possibly use
this issue to obtain sensitive information. (CVE-2026-6429)</p>
<p>It was discovered that curl could leak Digest authentication state when
switching proxies in some situations. A remote attacker could possibly use
this issue to obtain sensitive information. (CVE-2026-7168)</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-8227-1"/>
  </entry>
</feed>
