CVE-2026-1965

bad reuse of HTTP Negotiate connection

Published Mar 11, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
libcurl can in some circumstances reuse the wrong connection when asked to do
an Negotiate-authenticated HTTP or HTTPS request.

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 criterion must first 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. One underlying reason being that
Negotiate sometimes authenticates *connections* and not *requests*, contrary
to how HTTP is designed to work.

An application that allows Negotiate authentication to a server (that responds
wanting Negotiate) with `user1:password1` and then does another operation to
the same server also using Negotiate but with `user2:password2` (while the
previous connection is still alive) - the second request wrongly reused the
same connection and since it then sees that the Negotiate negotiation is
already made, it sends the request over that connection thinking it uses
the user2 credentials when it is in fact still using the connection
authenticated for user1...

The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`.

Applications can disable libcurl's reuse of connections and thus mitigate this
problem, by using one of the following libcurl options to alter how
connections are or are not reused: `CURLOPT_FRESH_CONNECT`,
`CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the
curl_multi API).

Analysis

AI-generated

Technical impact

libcurl has a flaw in its connection-reuse logic for Negotiate-authenticated HTTP or HTTPS requests. When an application authenticates a connection with one set of credentials (user1) and later issues another Negotiate request with a different set (user2) to the same server while the original connection is still open, the library incorrectly reuses the same socket. Because Negotiate can authenticate at the connection level, libcurl assumes the link is already authenticated and sends the second request using the original credentials. This improper authentication weakness, CWE-305, allows a client to access resources as a different user, permitting unauthorized data or service access.

Affected Systems

The vulnerability affects the curl:curl product, i.e., libcurl. No specific product‑version range is listed in the CVE record, so all releases prior to the fix are potentially impacted. The affected platform is identified by the CPE string cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*.

Risk and Exploitability

The CVSS base score is 6.5, which classifies the issue as Medium severity. The EPSS score is reported as less than 1 %, indicating a low probability that the vulnerability will be actively exploited at any given time. The vulnerability is not included in the CISA KEV catalog. Based on the description, the likely attack vector involves an application that performs two Negotiate-authenticated requests to the same server with different credentials; an attacker who controls the application or its configuration can drive the second request to reuse the prior connection, achieving unauthorized access. Exploitation requires the client to make both requests to the same server while the original connection remains open, and does not require any special permissions or lateral movement once the client is compromised.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libcurl to a version that contains the fix for CVE-2026-1965.
  • If an upgrade is not immediately possible, configure the library to disallow connection reuse by setting CURLOPT_FRESH_CONNECT to 1 (or CURLOPT_MAXCONNECTS to 1, or, for curl_multi, CURLMOPT_MAX_HOST_CONNECTIONS to 1).
  • Verify after configuration that subsequent Negotiate requests do not reuse connections from different credential sets.

Generated by OpenCVE AI on September 21, 2026 at 07:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8084-1 curl vulnerabilities
Ubuntu USN Ubuntu USN USN-8099-1 curl vulnerabilities
History
Type Values Removed Values Added
Description libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. 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 criterion must first 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. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API). libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. 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 criterion must first 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. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API).
Type Values Removed Values Added
First Time appeared Haxx
Haxx curl
CPEs cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*
Vendors & Products Haxx
Haxx curl
Type Values Removed Values Added
First Time appeared Curl
Curl curl
Vendors & Products Curl
Curl curl
Type Values Removed Values Added
Weaknesses CWE-305
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. 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 criterion must first 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. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API).
Title bad reuse of HTTP Negotiate connection
References
Weaknesses
  • CWE-303

    Incorrect Implementation of Authentication Algorithm

  • CWE-305

    Authentication Bypass by Primary Weakness

Sources

Status
PUBLISHED
Assigner
curl
Published
Updated
Sep 15, 2026, 6:02 AM
Reserved
Feb 5, 2026, 11:00 AM
Status
Modified
Published
Mar 11, 2026, 11:15 AM
Modified
Sep 15, 2026, 7:16 AM
Severity
Moderate
Public date
Mar 11, 2026, 10:08 AM