CVE-2026-5545

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>linux-c7-curl</name>
	<range><lt>8.20.0</lt></range>
      </package>
      <package>
	<name>linux-rl9-curl</name>
	<range><lt>8.20.0</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.

libcurl
	features a pool of recent connections so that subsequent requests
	can
reuse an existing connection to avoid overhead.

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.

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's and user2's credentials
	when it is in fact
still using the connection authenticated for
	user1...</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-5545</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-5545</url>
    </references>
    <dates>
      <discovery>2026-05-13</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>