<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 10:06:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-5545 — wrong reuse of HTTP Negotiate connection</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-5545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; curl&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; curl&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-5545</guid>
    </item>
    <item>
      <title>USN-8227-1 — curl vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8227-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8227-1</guid>
    </item>
  </channel>
</rss>
