Description
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". 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 services.
Affected products
haxx: curl
References4
- curl.se/docs/CVE-2026-8458.html PatchVendor Advisory
- curl.se/docs/CVE-2026-8458.json Vendor Advisory
- hackerone.com/reports/3721183 ExploitIssue TrackingThird Party Advisory
- hackerone.com/reports/3721183 ExploitIssue TrackingThird Party Advisory
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N - EPSS — exploit probability
- 0% percentile: 32 · as of 16 November 2026
- CWE
- CWE-488
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.