CVE-2026-8458
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- EPSS probability
- 0.37%
- CWE
- CWE-488
- Published
- 2026-07-03
- Last modified
- 2026-09-17
Affected products
- curl curl
- curl curl
- curl curl
- curl curl
- curl curl
- curl curl
- curl curl
- curl curl
Weakness type
Related vulnerabilities
- CVE-2025-47928 — Spotipy repo vulnerable to secrets exfiltration via `pull_request_target`
- CVE-2026-16498 — terraform-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode
- CVE-2026-16326 — consul-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode
- CVE-2026-19931 — Negotiate ambient user conn reuse
- CVE-2024-38367 — CoacoaPods trunk sessions verification step could be manipulated for owner session hijacking
- CVE-2023-1907 — Pgadmin: users authenticated simultaneously via ldap may be attached to the wrong session
- CVE-2024-6162 — Undertow: url-encoded request path information can be broken on ajp-listener
- CVE-2024-5148 — Gnome-remote-desktop: inadequate validation of session agents using d-bus methods may expose rdp tls certificate