CVE-2026-1965

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).

• CWE-305

• https://curl.se/docs/CVE-2026-1965.htmlPatch, Vendor Advisory
• https://curl.se/docs/CVE-2026-1965.jsonVendor Advisory

Published

Mar 11, 2026

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-19594Insufficient input sanitization in Snowflake Python API (`sn…8.1
• CVE-2026-1960Stored Cross-Site Scripting (XSS) vulnerability in Loggro Py…5.1
• CVE-2026-1961A flaw was found in Foreman. A remote attacker could exploit…8
• CVE-2026-1962A vulnerability has been found in WeKan up to 8.20. The impa…9.8
• CVE-2026-1963A vulnerability was found in WeKan up to 8.20. This affects …9.8
• CVE-2026-1964A vulnerability was determined in WeKan up to 8.20. This imp…5.3
• CVE-2026-1966YugabyteDB Anywhere displays LDAP bind passwords configured …2.4
• CVE-2026-1969The trx_addons WordPress plugin before 2.38.5 does not corre…5.3
• CVE-2026-1970A flaw has been found in Edimax BR-6258n up to 1.18. This is…6.1
• CVE-2026-1971A vulnerability has been found in Edimax BR-6288ACL up to 1.…4.8
• CVE-2026-1972A vulnerability was found in Edimax BR-6208AC 2_1.02. The af…7.5
• CVE-2026-1973A vulnerability was determined in Free5GC up to 4.1.0. The i…7.5